Re: Re: Add minor version to v3 protocol to allow changes without breaking backwards compatibility

Merlin Moncure <mmoncure@gmail.com>

From: Merlin Moncure <mmoncure@gmail.com>

To: Robert Haas <robertmhaas@gmail.com>

Cc: Noah Misch <noah@leadboat.com>, Florian Weimer <fweimer@bfk.de>, Ants Aasma <ants.aasma@eesti.ee>, Mikko Tiihonen <mikko.tiihonen@nitorcreations.com>, pgsql-hackers@postgresql.org

Date: 2012-01-23T21:54:30Z

Lists: pgsql-hackers

On Mon, Jan 23, 2012 at 3:06 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> Not being responsible from the maintenance of any PostgreSQL drivers
> whatsoever, I don't have a strong feeling about which of these is the
> case, and I'd like us to hear from the people who do.

I'm just gonna come right out and say that GUC-based solutions are not
the way -- bytea encoding change is a perfect example of that.
IMSNHO, there's only two plausible paths ahead:

1) document the binary formats and continue with 'go at your own risk'
2) full auto-negotiation for all wire formats (text and binary).

merlin