| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Henshall, Stuart - WCP" <SHenshall(at)westcountrypublications(dot)co(dot)uk> |
| Cc: | "'pgsql-bugs(at)postgresql(dot)org'" <pgsql-bugs(at)postgresql(dot)org>, Vadim Mikheev <vmikheev(at)sectorbase(dot)com> |
| Subject: | Re: After ~Crash Sequence not correct |
| Date: | 2001-12-19 16:02:53 |
| Message-ID: | 29955.1008777773@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Henshall, Stuart - WCP" <SHenshall(at)westcountrypublications(dot)co(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-12-19 17:39:18 | Re: After ~Crash Sequence not correct |
| Previous Message | Tom Lane | 2001-12-19 15:06:26 | Re: Bug #544: Upgrade to 7.1 - sequence permissions not restored |