Re: Bug with dump/restore when using UNION and ORDER BY in views - Mailing list pgsql-sql

From Christopher Kings-Lynne
Subject Re: Bug with dump/restore when using UNION and ORDER BY in views
Date
Msg-id 00a801c23b77$24bd2dc0$0200a8c0@SOL
Whole thread Raw
In response to Bug with dump/restore when using UNION and ORDER BY in views  ("Kristian Eide" <kreide@online.no>)
Responses Re: Bug with dump/restore when using UNION and ORDER BY in views  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-sql
> 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




pgsql-sql by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bug with dump/restore when using UNION and ORDER BY in views
Next
From: Tom Lane
Date:
Subject: Re: Bug with dump/restore when using UNION and ORDER BY in views