Fix pg_dump to do the right thing when escaping the contents of large objects.
The previous implementation got it right in most cases but failed in one:
if you pg_dump into an archive with standard_conforming_strings enabled, then
pg_restore to a script file (not directly to a database), the script will set
standard_conforming_strings = on but then emit large object data as
At the moment the code is made to emit hex-format bytea strings when dumping
to a script file. We might want to change to old-style escaping for backwards
compatibility, but that would be slower and bulkier. If we do, it's just a
matter of reimplementing appendByteaLiteral().
This has been broken for a long time, but given the lack of field complaints
I'm not going to worry about back-patching.
dumputils.c (r1.47 -> r1.48)
dumputils.h (r1.24 -> r1.25)
pg_backup_archiver.c (r1.173 -> r1.174)
pg_backup_archiver.h (r1.80 -> r1.81)
pg_backup_null.c (r1.21 -> r1.22)
pgsql-committers by date
|Next:||From: Peter Eisentraut||Date: 2009-08-04 22:04:37|
|Subject: pgsql: Use DocBook XSL stylesheets for man page building This switches |
|Previous:||From: Alvaro Herrera||Date: 2009-08-04 21:22:46|
|Subject: pgsql: Avoid including miscadmin.h into plpgsql.h; instead include it |