"Mason Hale" <[EMAIL PROTECTED]> writes:
> On 4/14/07, Tom Lane <[EMAIL PROTECTED]> wrote:
>> The methodology that pre-8.2 pg_dump uses for serial columns is
>> vulnerable to quite a number of problems if serial sequences don't have
>> the expected names, and this seems to be another one.
> I assu
On 4/14/07, Tom Lane <[EMAIL PROTECTED]> wrote:
Hmm ... which sequence is entry.id actually referring to on the source
database? I suspect that it is linked to some differently-named
sequence like "entry_id_seq1" and the source's "entry_id_seq" is not
in truth doing anything (and, in particular
"Mason Hale" <[EMAIL PROTECTED]> writes:
> After running pg_dump to backup my database, and then running pg_restore to
> load the db (on a different server),
> I run into a problem with creating a sequence.
Hmm ... which sequence is entry.id actually referring to on the source
database? I suspect
Hello -
After running pg_dump to backup my database, and then running pg_restore to
load the db (on a different server),
I run into a problem with creating a sequence. After the pg_restore is
completed, the sequence is created, but
the value is not set correctly. As a result calls nextval for the
