aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2014-06-12 20:14:32 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2014-06-12 20:14:32 -0400
commitc81e63d85f0c2c39d3fdfd8b95fc1ead6fdcb89f (patch)
treed27eac50a265559a7bbc174ab98c8a2774c8c912 /contrib/postgres_fdw/postgres_fdw.c
parent6554656ea2043c5bb877b427237dc5ddd7c5e5c8 (diff)
downloadpostgresql-c81e63d85f0c2c39d3fdfd8b95fc1ead6fdcb89f.tar.gz
postgresql-c81e63d85f0c2c39d3fdfd8b95fc1ead6fdcb89f.zip
Fix pg_restore's processing of old-style BLOB COMMENTS data.
Prior to 9.0, pg_dump handled comments on large objects by dumping a bunch of COMMENT commands into a single BLOB COMMENTS archive object. With sufficiently many such comments, some of the commands would likely get split across bufferloads when restoring, causing failures in direct-to-database restores (though no problem would be evident in text output). This is the same type of issue we have with table data dumped as INSERT commands, and it can be fixed in the same way, by using a mini SQL lexer to figure out where the command boundaries are. Fortunately, the COMMENT commands are no more complex to lex than INSERTs, so we can just re-use the existing lexer for INSERTs. Per bug #10611 from Jacek Zalewski. Back-patch to all active branches.
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions