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

From Henshall, Stuart - WCP
Subject After ~Crash Sequence not correct
Date
Msg-id E2870D8CE1CCD311BAF50008C71EDE8E01F7475E@MAIL_EXCHANGE
Whole thread Raw
Responses Re: After ~Crash Sequence not correct  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: After ~Crash Sequence not correct  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Severity: Annoyance
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. (I *think* it was a
different table & sequence last time).
- Stuart

pgsql-bugs by date:

Previous
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #544: Upgrade to 7.1 - sequence permissions not restored
Next
From: Tom Lane
Date:
Subject: Re: Bug #544: Upgrade to 7.1 - sequence permissions not restored