| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | 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 02:29:21 |
| Message-ID: | 28761.1127442561@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> This item has been added to the 8.1 bugs list:
> http://momjian.postgresql.org/cgi-bin/pgbugs
This isn't going to be fixed for 8.1. I think it's really a variant of
the TODO item
o %Have ALTER TABLE RENAME rename SERIAL sequence names
To my mind the appropriate fix is to come up with some arrangement
that allows the stored form of NEXTVAL(seq) to specify the referenced
sequence directly (by OID) rather than as a text string. There are some
speculations about this in the archives, but no really workable solution
yet.
(wanders off, wondering if a "regclass" literal value would help ...)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-09-23 02:59:43 | Re: BUG #1883: Renaming a schema leaves inconsistent sequence |
| Previous Message | Bruce Momjian | 2005-09-23 02:13:30 | Re: BUG #1883: Renaming a schema leaves inconsistent sequence |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2005-09-23 02:55:13 | Re: PCTFree Results |
| Previous Message | Bruce Momjian | 2005-09-23 02:26:34 | Re: Spinlocks, yet again: analysis and proposed patches |