Re: BUG #1883: Renaming a schema leaves inconsistent sequence

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Kouber Saparev <postgresql(at)saparev(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1883: Renaming a schema leaves inconsistent sequence
Date: 2005-09-23 04:35:02
Message-ID: 29758.1127450102@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

I wrote:
> If I recall the previous discussions correctly there were still some
> gotchas :-(

One point that comes to mind after more thought is that you'd really
like "create table ... default nextval('foo') ..." to understand that
there is a dependency from the column's default expression to sequence
foo. Currently we hack this to sort-of-work for SERIAL columns, but
I'd like to have a cleaner mechanism.

Is it sane for a literal like 'foo'::regclass to, in itself, create a
dependency? Not sure.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Trevor Tingey 2005-09-23 04:42:16 BUG #1905: When a column with the chkpass datatype is used in a where clause it returns invalid results
Previous Message Tom Lane 2005-09-23 04:12:23 Re: BUG #1883: Renaming a schema leaves inconsistent sequence

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2005-09-23 04:44:51 Re: Gerbil build farm failure
Previous Message Tom Lane 2005-09-23 04:12:23 Re: BUG #1883: Renaming a schema leaves inconsistent sequence