Re: renaming table leaves constraint behind [7.3.2]

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Holger Klawitter <lists(at)klawitter(dot)de>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: renaming table leaves constraint behind [7.3.2]
Date: 2003-02-10 19:21:09
Message-ID: 16004.1044904869@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Holger Klawitter <lists(at)klawitter(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ed L. 2003-02-10 19:31:54 Re: 7.3.2: test select_having ... FAILED
Previous Message Dave Smith 2003-02-10 19:04:34 Why must SELECT DISTINCT, ORDER BY expressions must appear in target list?