Re: PostgreSQL 9.1 pg_dump setval() sets wrong value

Поиск
Список
Период
Сортировка
От Greg Donald
Тема Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
Дата
Msg-id CAO+WgCYKOZJkwqtEOdfLiLtmBwmHRCpG3hxEQK9afW+7Q0AenA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: PostgreSQL 9.1 pg_dump setval() sets wrong value  (Adrian Klaver <adrian.klaver@gmail.com>)
Ответы Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
Список pgsql-general
On Wed, Dec 28, 2011 at 9:30 AM, Adrian Klaver <adrian.klaver@gmail.com> wrote:
> Wonder if it is related to this:
> http://archives.postgresql.org/pgsql-bugs/2011-11/msg00098.php

None of my sequences are named 'new'.  What do you mean?

> 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.

That's an option.  When I upgraded to PostgreSQL 9.1 on my Ubuntu
11.10 workstation, I noticed apt did not make me uninstall my old 8.4
version.  Seemed happy to leave them both installed.


I found a number of sequence fixing options:

http://stackoverflow.com/questions/244243/how-to-reset-postgres-primary-key-sequence-when-it-falls-out-of-sync


Right now I just have a long list of

ALTER SEQUENCE sequence_name RESTART WITH (SELECT max(id) FROM table_name);

to fix things up for me on my local setup.


--
Greg Donald

В списке pgsql-general по дате отправления:

Предыдущее
От: Adrian Klaver
Дата:
Сообщение: Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
Следующее
От: Greg Donald
Дата:
Сообщение: Re: PostgreSQL 9.1 pg_dump setval() sets wrong value