Re: [JDBC] Optimize postgres protocol for fixed size arrays

On 25 November 2011 07:54, Mikko Tiihonen
<mikko(dot)tiihonen(at)nitorcreations(dot)com> wrote:

> <=BE ParameterStatus(binary_minor = 23)
> FE=> Execute(SET binary_minor = 20)

Yeah this was almost exactly what I was thinking about how to retrofit
it, except it might be clearer to have, say, "supported_binary_minor"
(read-only, advertised by the server on startup) vs. "binary_minor"
(read-write, defaults to 0) as otherwise you have special behavior for
just one parameter where the advertised version doesn't actually match
the currently-set version.

Re list vs. always-incrementing minor version, you could just use an
integer and set bits to represent features, which would keep it simple
but also let clients be more selective about which features they
implement (you could support feature 21 and 23 without supporting 22)

Oliver