Re: renaming table leaves constraint behind [7.3.2] - Mailing list pgsql-general

From Tom Lane
Subject Re: renaming table leaves constraint behind [7.3.2]
Date
Msg-id 16004.1044904869@sss.pgh.pa.us
Whole thread Raw
In response to renaming table leaves constraint behind [7.3.2]  (Holger Klawitter <lists@klawitter.de>)
Responses Re: renaming table leaves constraint behind [7.3.2]  (Holger Klawitter <lists@klawitter.de>)
List pgsql-general
Holger Klawitter <lists@klawitter.de> writes:
> the following code throws an error (which it didn't in 7.2.x):

Sure it did.  The error message seems to have changed a trifle, but
you'd get a conflict on the index name in either case.

This isn't real desirable ... but having ALTER TABLE RENAME run around
and rename associated indexes might create issues too ...

            regards, tom lane

pgsql-general by date:

Previous
From: Dave Smith
Date:
Subject: Why must SELECT DISTINCT, ORDER BY expressions must appear in target list?
Next
From: "Ed L."
Date:
Subject: Re: 7.3.2: test select_having ... FAILED