Skip site navigation (1) Skip section navigation (2)

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

From: Ants Aasma <ants(dot)aasma(at)eesti(dot)ee>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Mikko Tiihonen <mikko(dot)tiihonen(at)nitorcreations(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers(at)postgresql(dot)org, Merlin Moncure <mmoncure(at)gmail(dot)com>
Subject: Re: Re: Add minor version to v3 protocol to allow changes without breaking backwards compatibility
Date: 2012-01-21 10:51:55
Message-ID: CA+CSw_tk7auo=Vkx4tj5_KK4RrBsB_2K4LykLYcNk9HvupoCDQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 19 Jan 2012 21:00, "Robert Haas" <robertmhaas(at)gmail(dot)com> wrote:
> I agree.  It occurs to me that we recently changed the default *text*
> output format for bytea for reasons not dissimilar to those
> contemplated here.  Presumably, that's a much more disruptive change,
> and yet we've had minimal complaints because anyone who gets bitten
> can easily set bytea_output='escape' and the problem goes away.

I had a run in with this. JDBC driver versions < 9.0 with the default
configuration resulted in silent data corruption. The fix was easy, but not
having an useful error was what really bothered me.

--
Ants Aasma

In response to

Responses

pgsql-hackers by date

Next:From: Marc MaminDate: 2012-01-21 11:52:34
Subject: Re: Speed dblink using alternate libpq tuple storage
Previous:From: Thomas MunroDate: 2012-01-21 10:14:47
Subject: Re: WIP -- renaming implicit sequences

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group