Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
| От | Adrian Klaver |
|---|---|
| Тема | Re: PostgreSQL 9.1 pg_dump setval() sets wrong value |
| Дата | |
| Msg-id | 201112280730.29932.adrian.klaver@gmail.com обсуждение исходный текст |
| Ответ на | 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 |
On Wednesday, December 28, 2011 7:18:01 am Greg Donald wrote: > On Wed, Dec 28, 2011 at 9:07 AM, Adrian Klaver <adrian.klaver@gmail.com> wrote: > > So how are the sequences being tied to the tables? In your previous post > > the table definitions did not show a SERIAL type or a default of > > nextval(). > > The id columns were created using "id serial NOT NULL". > > I've gone back this morning and pulled older backups, from when I was > using pg_dump that came with my PostgreSQL 8.4 install. Those backups > look fine to me, all the setval() calls are there and correct. So it > looks like a problem with the new pg_dump best I can tell. Wonder if it is related to this: http://archives.postgresql.org/pgsql-bugs/2011-11/msg00098.php Might want to file bug report: http://www.postgresql.org/support/submitbug/ In the meantime what about using 8.4 pg_dump to create dump file and then using that file to load 9.1 server. -- Adrian Klaver adrian.klaver@gmail.com
В списке pgsql-general по дате отправления: