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.
In response to
pgsql-hackers by date
|Next:||From: Marc Mamin||Date: 2012-01-21 11:52:34|
|Subject: Re: Speed dblink using alternate libpq tuple storage|
|Previous:||From: Thomas Munro||Date: 2012-01-21 10:14:47|
|Subject: Re: WIP -- renaming implicit sequences|