Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
| От | Tom Lane |
|---|---|
| Тема | Re: PostgreSQL 9.1 pg_dump setval() sets wrong value |
| Дата | |
| Msg-id | 7487.1325113075@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: PostgreSQL 9.1 pg_dump setval() sets wrong value (Greg Donald <gdonald@gmail.com>) |
| Ответы |
Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
Re: PostgreSQL 9.1 pg_dump setval() sets wrong value |
| Список | pgsql-general |
Greg Donald <gdonald@gmail.com> writes:
> My pg_dump backups from before 9.1.1 were correct, now they are not:
> diff backup_20111212031701.sql backup_20111223013539.sql | grep setval
> | grep state_id
> < SELECT pg_catalog.setval('cp_state_id_seq', 52, true);
> > SELECT pg_catalog.setval('cp_state_id_seq', 1, false);
These "grep" calls are showing just exactly not enough to prove
anything. I remain unclear as to what state is actually in the
database, or what is being dumped, but I suspect at this point that you
may have multiple sequences of the same names in different schemas.
regards, tom lane
В списке pgsql-general по дате отправления: