Skip site navigation (1) Skip section navigation (2)

pgsql: Fix several problems in pg_dump's handling of SQL/MED objects,

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix several problems in pg_dump's handling of SQL/MED objects,
Date: 2010-07-14 21:21:23
Message-ID: 20100714212123.D5D5C7541D5@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Fix several problems in pg_dump's handling of SQL/MED objects, notably failure
to dump a PUBLIC user mapping correctly, as per bug #5560 from Shigeru Hanada.
Use the pg_user_mappings view rather than trying to access pg_user_mapping
directly, so that the code doesn't fail when run by a non-superuser.  And
clean up some minor carelessness such as unsafe usage of fmtId().

Back-patch to 8.4 where this code was added.

Tags:
----
REL8_4_STABLE

Modified Files:
--------------
    pgsql/src/bin/pg_dump:
        pg_dump.c (r1.539.2.4 -> r1.539.2.5)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dump.c?r1=1.539.2.4&r2=1.539.2.5)

pgsql-committers by date

Next:From: Tom LaneDate: 2010-07-14 22:04:21
Subject: pgsql: Use an <xref> for restore_command reference.
Previous:From: Tom LaneDate: 2010-07-14 21:21:16
Subject: pgsql: Fix several problems in pg_dump's handling of SQL/MED objects,

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group