pgsql: Fix pg_dump's --if-exists for large objects

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix pg_dump's --if-exists for large objects
Date: 2014-09-30 15:08:28
Message-ID: E1XYz2S-0007zT-Kc@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix pg_dump's --if-exists for large objects

This was born broken in 9067310cc5dd590e36c2c3219dbf3961d7c9f8cb.

Per trouble report from Joachim Wieland.

Pavel Stěhule and Álvaro Herrera

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/fd02931a6c83bf3beb2d03f65700600787d569a3

Modified Files
--------------
src/bin/pg_dump/pg_backup_archiver.c | 99 +++++++++++++++++++---------------
1 file changed, 57 insertions(+), 42 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Stephen Frost 2014-09-30 20:00:53 pgsql: Correct stdin/stdout usage in COPY .. PROGRAM
Previous Message Bruce Momjian 2014-09-30 00:20:07 pgsql: pg_upgrade: have pg_upgrade fail for old 9.4 JSONB format