From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: Bug with dump/restore when using UNION and ORDER BY in views
Date: Sun, 4 Aug 2002 13:24:00 +0800
Message-ID: <00a801c23b77$24bd2dc0$0200a8c0@SOL> (raw)
References: <036501c23b32$5c5149f0$6b97f181@speed>
<6562.1028430401@sss.pgh.pa.us>
> Yeah. This is fixed in current sources, and I back-patched it into
> the REL7_2 branch, but current plans don't seem to include a 7.2.2
> release --- we'll be going straight to 7.3 beta instead.
Is it worth doing a 7.2.2 patch that will dump people's foreign keys as
ALTER TABLE/ADD FOREIGN KEY instead of a bunch of CREATE CONSTRAINT
TRIGGERs, so that they actually become constraints in 7.3?
Also Tom - did you check if you can CREATE CONSTRAINT TRIGGER on a dropped
column - I think I neglected to look at that in the patch I submitted
originally.
Chris
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-sql@postgresql.org
Cc: chriskl@familyhealth.com.au, tgl@sss.pgh.pa.us
Subject: Re: Bug with dump/restore when using UNION and ORDER BY in views
In-Reply-To: <00a801c23b77$24bd2dc0$0200a8c0@SOL>
* 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