James William Pye wrote:
> The use case primarily applies to custom clients(non-libpq, atm) that
> support multiple PQ versions that may be implemented in separate
> modules/libraries. (Avoid loading client-2.0 code for a 3.0 connection,
> and/or future versions.)
>
> libpq "automatically negotiates" the version using trial and error,
> effectively(assume 3.0 by sending 'S', if 'E', fallback to 2.0, and
> reestablish the connection, apparently).
The JDBC driver does exactly the same (or you can explicitly specify a
protocol version to use) and is effectively loading code on demand
anyway, being Java -- but I've seen no problems with the current
approach. I think you're trying tho fix a problem that doesn't exist.
-O