Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 6E70D635221 for ; Thu, 2 Jul 2009 18:34:40 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 30827-05 for ; Thu, 2 Jul 2009 18:34:39 -0300 (ADT) Received: from cvs.postgresql.org (cvs.postgresql.org [217.196.146.206]) by mail.postgresql.org (Postfix) with ESMTP id 76E1D6352D2 for ; Thu, 2 Jul 2009 18:34:39 -0300 (ADT) Received: by cvs.postgresql.org (Postfix, from userid 1007) id 52C2975331E; Thu, 2 Jul 2009 21:34:38 +0000 (UTC) MIME-Version: 1.0 To: pgsql-committers@postgresql.org Subject: pgsql: Fix up pg_dump's --binary-upgrade option so that it behaves X-Mailer: activitymail 1.24, http://search.cpan.org/dist/activitymail/ Content-Type: text/plain Message-Id: <20090702213438.52C2975331E@cvs.postgresql.org> Date: Thu, 2 Jul 2009 21:34:38 +0000 (UTC) From: tgl@postgresql.org (Tom Lane) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200907/20 X-Sequence-Number: 37623 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)