Excerpts from Thom Brown's message of jue nov 04 09:05:01 -0300 2010:
> This would be instead of having to do:
> CREATE SEQUENCE id_stuff_seq;
> SELECT setval('id_stuff_seq', (SELECT max(id) FROM stuff))
> ALTER TABLE stuff ALTER COLUMN id SET DEFAULT
> Which would also mean the sequence would not get dropped with the table.
You can fix that with an ALTER SEQUENCE OWNED BY.
> Abhorrent idea, or acceptable?
I think the problem is in locking the table against futher insertions
while you do the setval.
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
In response to
pgsql-hackers by date
|Next:||From: Daniele Varrazzo||Date: 2010-11-04 16:46:28|
|Subject: Re: psycopg and two phase commit|
|Previous:||From: Alvaro Herrera||Date: 2010-11-04 15:50:51|
|Subject: Re: ALTER OBJECT any_name SET SCHEMA name|