Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id C4DAE47549E for ; Sun, 4 Aug 2002 01:23:52 -0400 (EDT) Received: from mail.iinet.net.au (symphony-01.iinet.net.au [203.59.3.33]) by postgresql.org (Postfix) with SMTP id 497CB475396 for ; Sun, 4 Aug 2002 01:23:51 -0400 (EDT) Received: (qmail 3087 invoked by uid 666); 4 Aug 2002 05:23:46 -0000 Received: from unknown (HELO SOL) (203.59.103.215) by mail.iinet.net.au with SMTP; 4 Aug 2002 05:23:46 -0000 Message-ID: <00a801c23b77$24bd2dc0$0200a8c0@SOL> From: "Christopher Kings-Lynne" To: "Tom Lane" Cc: References: <036501c23b32$5c5149f0$6b97f181@speed> <6562.1028430401@sss.pgh.pa.us> Subject: Re: Bug with dump/restore when using UNION and ORDER BY in views Date: Sun, 4 Aug 2002 13:24:00 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200208/74 X-Sequence-Number: 8920 > 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