| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 03:12:28 |
| Message-ID: | 20050923031227.GK31459@surnet.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Thu, Sep 22, 2005 at 10:29:21PM -0400, Tom Lane wrote:
> 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 ...)
Wouldn't it be easy to create a nextval(oid) function, and have SERIAL
emit that instead?
--
Alvaro Herrera Architect, http://www.EnterpriseDB.com
"Endurecerse, pero jamás perder la ternura" (E. Guevara)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-09-23 04:12:23 | Re: BUG #1883: Renaming a schema leaves inconsistent sequence |
| Previous Message | Bruce Momjian | 2005-09-23 02:59:43 | Re: BUG #1883: Renaming a schema leaves inconsistent sequence |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2005-09-23 03:30:35 | SQL/XML public functions documentation for PostgreSQL 8.2 |
| Previous Message | Bruce Momjian | 2005-09-23 03:05:49 | Re: [HACKERS] How to determine date / time of last postmaster |