Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
| От | Adrian Klaver |
|---|---|
| Тема | Re: PostgreSQL 9.1 pg_dump setval() sets wrong value |
| Дата | |
| Msg-id | 201112280820.08397.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:51:24 am Greg Donald wrote: > 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? I was thinking of the more generic case. The problem with 'new' in the above bug is that it is a reserved word and the list of reserved words recognized by pg_dump changed in 9.0 or 9.1(?). If the table definitions you showed are correct you have sequence columns named id. id is in the list of reserved words also: http://www.postgresql.org/docs/9.1/static/sql-keywords-appendix.html -- Adrian Klaver adrian.klaver@gmail.com
В списке pgsql-general по дате отправления: