aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistget.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-01-21 16:22:21 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2011-01-21 16:22:21 -0500
commit2a1ef1011548e329f4eca86671401bf4124f9d1e (patch)
tree58798b0c936832b4e70edb88fd0cb175560f5464 /src/backend/access/gist/gistget.c
parent9de3f2843c4cf695a37d04d268df350b6118a232 (diff)
downloadpostgresql-2a1ef1011548e329f4eca86671401bf4124f9d1e.tar.gz
postgresql-2a1ef1011548e329f4eca86671401bf4124f9d1e.zip
Fix pg_restore to do the right thing when escaping large objects.
Specifically, this makes the workflow pg_dump -Fc -> pg_restore -> file produce correct output for BLOBs when the source database has standard_conforming_strings turned on. It was already okay when that was off, or if pg_restore was told to restore directly into a database. This is a back-port of commit b1732111f233bbb72788e92a627242ec28a85631 of 2009-08-04, with additional changes to emit old-style escaped bytea data instead of hex-style. At the time, we had not heard of anyone encountering the problem in the field, so I judged it not worth the risk of changing back branches. Now we do have a report, from Bosco Rama, so back-patch into 8.2 through 8.4. 9.0 and up are okay already.
Diffstat (limited to 'src/backend/access/gist/gistget.c')
0 files changed, 0 insertions, 0 deletions