Re: After ~Crash Sequence not correct - Mailing list pgsql-bugs

From Tom Lane
Subject Re: After ~Crash Sequence not correct
Date
Msg-id 29955.1008777773@sss.pgh.pa.us
Whole thread Raw
In response to After ~Crash Sequence not correct  ("Henshall, Stuart - WCP" <SHenshall@westcountrypublications.co.uk>)
List pgsql-bugs
"Henshall, Stuart - WCP" <SHenshall@westcountrypublications.co.uk> writes:
> Setup: PostgreSQL 7.1.2 on Dual PIII WinNT4 server + Cygwin 1.3.2
> PostgreSQL is run as a service and when rebooting (which doesn't shutdown -
> previously on cygwin list (hence the ~Crash in title)) I have twice noticed
> that a sequence was not properly updated, however records with Primary keys
> based upon the sequence where present in the table.

Hmm.  You're about the third person to report something like this, so
there's clearly something not right.  I'm guessing a bug in the WAL
logging or redo code for sequences ...

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bug #544: Upgrade to 7.1 - sequence permissions not restored
Next
From: Tom Lane
Date:
Subject: Re: After ~Crash Sequence not correct