Arnaud Lesauvage <arnaud(dot)listes(at)codata(dot)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
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
In response to
pgsql-odbc by date
|Next:||From: Arnaud Lesauvage||Date: 2010-07-06 15:02:43|
|Subject: Re: 'default nextval()' loses schema-qualification in dump
|Previous:||From: Arnaud Lesauvage||Date: 2010-07-06 10:02:30|
|Subject: 'default nextval()' loses schema-qualification in dump ?|
pgsql-general by date
|Next:||From: ChronicDB Community Team||Date: 2010-07-06 14:51:24|
|Subject: Feedback on live schema changes and updates for PostgreSQL|
|Previous:||From: Alban Hertroys||Date: 2010-07-06 14:09:26|
|Subject: Re: Rules in views, how to?|