pgsql: Fix up pg_dump's treatment of large object ownership and ACLs.

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix up pg_dump's treatment of large object ownership and ACLs.
Date: 2010-02-18 01:29:10
Message-ID: 20100218012910.D51AF7541C5@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Fix up pg_dump's treatment of large object ownership and ACLs. We now emit
a separate archive entry for each BLOB, and use pg_dump's standard methods
for dealing with its ownership, ACL if any, and comment if any. This means
that switches like --no-owner and --no-privileges do what they're supposed
to. Preliminary testing says that performance is still reasonable even
with many blobs, though we'll have to see how that shakes out in the field.

KaiGai Kohei, revised by me

Modified Files:
--------------
pgsql/src/bin/pg_dump:
dumputils.c (r1.53 -> r1.54)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/dumputils.c?r1=1.53&r2=1.54)
pg_backup_archiver.c (r1.178 -> r1.179)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_backup_archiver.c?r1=1.178&r2=1.179)
pg_backup_archiver.h (r1.83 -> r1.84)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_backup_archiver.h?r1=1.83&r2=1.84)
pg_backup_db.c (r1.87 -> r1.88)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_backup_db.c?r1=1.87&r2=1.88)
pg_backup_null.c (r1.23 -> r1.24)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_backup_null.c?r1=1.23&r2=1.24)
pg_dump.c (r1.571 -> r1.572)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dump.c?r1=1.571&r2=1.572)
pg_dump.h (r1.162 -> r1.163)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dump.h?r1=1.162&r2=1.163)
pg_dump_sort.c (r1.28 -> r1.29)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dump_sort.c?r1=1.28&r2=1.29)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2010-02-18 03:06:46 pgsql: Force READY portals into FAILED state when a transaction or
Previous Message User Fxjr 2010-02-18 01:23:27 npgsql - Npgsql2: Added missing comments.