Re: pg_dump fails to include sequences, leads to restore fail in any version
От | Alvaro Herrera |
---|---|
Тема | Re: pg_dump fails to include sequences, leads to restore fail in any version |
Дата | |
Msg-id | 20080617221401.GG10140@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: pg_dump fails to include sequences, leads to restore fail in any version ("Jeffrey Baker" <jwbaker@gmail.com>) |
Ответы |
Re: pg_dump fails to include sequences, leads to restore fail in any version
|
Список | pgsql-hackers |
Jeffrey Baker escribió: > The table was originally created this way: > > CREATE TABLE transaction > ( > transaction_id SERIAL PRIMARY KEY, > buyer_account_id INTEGER, > seller_account_id INTEGER, > date DATE, > item_id INTEGER, > source TEXT > ); Okay, but was it created on 8.1 or was it already created on an older version and restored? I don't see this behavior if I create it in 8.1 -- the field is dumped as SERIAL, unlike what you show. -- -- Name: transaction; Type: TABLE; Schema: public; Owner: alvherre; Tablespace: -- CREATE TABLE "transaction" ( transaction_id serial NOT NULL, buyer_account_id integer, seller_account_id integer, date date, item_id integer, source text ); $ pg_dump --version pg_dump (PostgreSQL) 8.1.10 -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
В списке pgsql-hackers по дате отправления: