Re: Making serial survive pg_dump
От | Rod Taylor |
---|---|
Тема | Re: Making serial survive pg_dump |
Дата | |
Msg-id | 06a001c21321$8b54e380$fe01a8c0@jester обсуждение исходный текст |
Ответ на | Making serial survive pg_dump ("Rod Taylor" <rbt@zort.ca>) |
Ответы |
Re: Making serial survive pg_dump
|
Список | pgsql-hackers |
-- Rod ----- Original Message ----- From: "Tom Lane" <tgl@sss.pgh.pa.us> To: "Rod Taylor" <rbt@zort.ca> Cc: "Hackers List" <pgsql-hackers@postgresql.org> Sent: Thursday, June 13, 2002 9:46 AM Subject: Re: [HACKERS] Making serial survive pg_dump > "Rod Taylor" <rbt@zort.ca> writes: > > Store sequence information in the SERIAL creation statement: > > CREATE TABLE tab (col1 SERIAL(<start num>, <sequence name>)); > > This is wrong because it loses the separation between schema and data. > I do agree that it would be nice if pg_dump recognized serial columns > and dumped them as such --- but the separate setval call is still the > appropriate technique for messing with the sequence contents. We do > not need a syntax extension in CREATE. Ok, keeping the setval is appropriate. Are there any problems with a SERIAL(<sequence name>) implementation?
В списке pgsql-hackers по дате отправления: