From: tgl@postgresql.org
To: pgsql-committers@postgresql.org
Subject: pgsql: Fix up pg_dump's --binary-upgrade option so that it behaves
Date: Thu, 2 Jul 2009 21:34:38 +0000 (UTC)
Message-ID: <20090702213438.52C2975331E@cvs.postgresql.org> (raw)
Log Message:
-----------
Fix up pg_dump's --binary-upgrade option so that it behaves properly with
inherited columns and check constraints. Per my recent trouble report.
Tags:
----
REL8_4_STABLE
Modified Files:
--------------
pgsql/src/bin/pg_dump:
pg_dump.c (r1.539 -> r1.539.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dump.c?r1=1.539&r2=1.539.2.1)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@postgresql.org
Subject: Re: pgsql: Fix up pg_dump's --binary-upgrade option so that it behaves
In-Reply-To: <20090702213438.52C2975331E@cvs.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox