Hi,
Yes, pgdiff shows the difference for a table that has fields with empty
bytea comparing 9.1devel and 8.4 pg_dump files!
Best regards,
Vladimir Kokovic, DP senior, Belgrade, Serbia
On Mon, Oct 18, 2010 at 5:45 PM, Alvaro Herrera
wrote:
> Excerpts from Vladimir Kokovic's message of sáb oct 16
Vladimir Kokovic writes:
> I think that empty bytea shoukd be like in 8.4, without \\x !
We could do that, but it seems completely cosmetic. The real problem
here is that you've got client-side code that doesn't understand the
hex-based format. It's going to break as soon as it sees a non-empty
Hi,
I think that empty bytea shoukd be like in 8.4, without \\x !
Best regards,
Vladimir Kokovic, DP senior, Belgrade, Serbia
On Mon, Oct 18, 2010 at 8:02 PM, Alvaro Herrera
wrote:
> Excerpts from Vladimir Kokovic's message of lun oct 18 14:50:30 -0300 2010:
> > Hi,
> >
> > Yes, pgdiff shows th
Excerpts from Vladimir Kokovic's message of lun oct 18 14:50:30 -0300 2010:
> Hi,
>
> Yes, pgdiff shows the difference for a table that has fields with empty
> bytea comparing 9.1devel and 8.4 pg_dump files!
Would it be enough to flip bytea_output?
--
Álvaro Herrera
The PostgreSQL Company - Co
Excerpts from Vladimir Kokovic's message of sáb oct 16 15:45:02 -0300 2010:
> Hi,
>
> I'm not sure whether it is OK, a blank format for bytea, which is presented
> in 9.1devel (pg_dump and psql)
Yeah, an empty bytea is now output differently by default (just like any
other bytea). The \x means "
Hi,
I'm not sure whether it is OK, a blank format for bytea, which is presented
in 9.1devel (pg_dump and psql)
Earlier versions (7, 8):
psql - signature bytea not null default '':: bytea
pg_dump - signature bytea default ''::bytea not null
postgresql.conf:
standard_conforming_strings = off
bytea
