Re: [GENERAL] 'default nextval()' loses schema-qualification in dump ?
От | Tom Lane |
---|---|
Тема | Re: [GENERAL] 'default nextval()' loses schema-qualification in dump ? |
Дата | |
Msg-id | 27289.1278426134@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | 'default nextval()' loses schema-qualification in dump ? (Arnaud Lesauvage <arnaud.listes@codata.eu>) |
Ответы |
Re: [GENERAL] 'default nextval()' loses schema-qualification in dump
?
|
Список | pgsql-odbc |
Arnaud Lesauvage <arnaud.listes@codata.eu> writes: > After some research, we found in psqlODBC's log that before the restore > psqlODBC was getting the sequence's nextval with a schema qualified > call, and after the restore the call was not schema qualified. > I checked in pg_attrdef before and after the dump/restore, and indeed > the "default nextval()" on this problematic table loses it's schema > qualification in the process. This is a pretty inadequate description of your problem. Let's see the exact SQL you are dealing with. Note that if the argument of nextval is a plain regclass constant, like nextval('seq'::regclass) then the constant is in fact a reference to a specific sequence. Whether it's displayed with a schema name depends on whether that sequence is visible in your search_path. regards, tom lane
В списке pgsql-odbc по дате отправления: