Fix placement of "SET row_security" command issuance in pg_dump. Somebody apparently threw darts at the code to decide where to insert these. They certainly didn't proceed by adding them where other similar SETs were handled. This at least broke pg_restore, and perhaps other use-cases too.
Branch ------ master Details ------- http://git.postgresql.org/pg/commitdiff/297b2c1ef9878f84a9951beadf831ef390227238 Modified Files -------------- src/bin/pg_dump/pg_backup_archiver.c | 17 ++++++----------- src/bin/pg_dump/pg_dump.c | 19 +++++++++++-------- 2 files changed, 17 insertions(+), 19 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
