From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Zoltan Boszormenyi <zb(at)cybertec(dot)at> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Steve Crawford <scrawford(at)pinpointresearch(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: TRUNCATE TABLE with IDENTITY |
Date: | 2008-03-25 16:43:36 |
Message-ID: | 200803251643.m2PGhaE24146@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Zoltan Boszormenyi wrote:
> All of them? PostgreSQL allow multiple SERIALs to be present,
> the standard allows only one IDENTITY column in a table.
> And what about this case below?
>
> CREATE TABLE t1 (id1 serial, ...);
> ALTER SEQUENCE seq_t1_id1 RESTART WITH 5432 CYCLE;
>
> or the equivalent
>
> CREATE SEQUENCE seq_t1_id1 START WITH 5432 CYCLE;
> CREATE TABLE t1 (id1 serial, ...);
> ALTER SEQUENCE seq_t1_id1 OWNED BY t1.id1;
>
> PostgreSQL doesn't keep the START WITH information.
> But it should to perform a "restart" on the sequence,
> using the minval in this case wouldn't be correct.
I do think we need to wait for the standard to be accepted before adding
them to the TODO list as standard-compliant additions, especially
because no one is asking for the syntax yet.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2008-03-25 16:45:45 | Re: TRUNCATE TABLE with IDENTITY |
Previous Message | Gregory Stark | 2008-03-25 16:43:22 | Re: writing a MIN(RECORD) aggregate |
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2008-03-25 16:45:45 | Re: TRUNCATE TABLE with IDENTITY |
Previous Message | Zoltan Boszormenyi | 2008-03-25 16:42:33 | Re: TRUNCATE TABLE with IDENTITY |