Re: Re: Add minor version to v3 protocol to allow changes without breaking backwards compatibility - Mailing list pgsql-hackers

From Ants Aasma
Subject Re: Re: Add minor version to v3 protocol to allow changes without breaking backwards compatibility
Date
Msg-id CA+CSw_tk7auo=Vkx4tj5_KK4RrBsB_2K4LykLYcNk9HvupoCDQ@mail.gmail.com
Whole thread Raw
In response to Re: Re: Add minor version to v3 protocol to allow changes without breaking backwards compatibility  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Re: Add minor version to v3 protocol to allow changes without breaking backwards compatibility  (Florian Weimer <fweimer@bfk.de>)
List pgsql-hackers
<p>On 19 Jan 2012 21:00, "Robert Haas" <<a href="mailto:robertmhaas@gmail.com">robertmhaas@gmail.com</a>>
wrote:<br/> > I agree.  It occurs to me that we recently changed the default *text*<br /> > output format for
byteafor reasons not dissimilar to those<br /> > contemplated here.  Presumably, that's a much more disruptive
change,<br/> > and yet we've had minimal complaints because anyone who gets bitten<br /> > can easily set
bytea_output='escape'and the problem goes away.<p>I had a run in with this. JDBC driver versions < 9.0 with the
defaultconfiguration resulted in silent data corruption. The fix was easy, but not having an useful error was what
reallybothered me.<p>--<br /> Ants Aasma 

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: WIP -- renaming implicit sequences
Next
From: "Marc Mamin"
Date:
Subject: Re: Speed dblink using alternate libpq tuple storage