| From: | Sean Chittenden <chitt(at)speakeasy(dot)net> |
|---|---|
| To: | PGBugs List <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #1276: Backend panics on SETVAL('..', 0)... |
| Date: | 2004-10-05 00:13:37 |
| Message-ID: | 676F5B32-1663-11D9-9F57-000A95C705DC@speakeasy.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> ERROR: setval: value 0 is out of bounds for sequence "foo_id_seq"
> (1..9223372036854775807)
> FATAL: block 0 of 1663/97972/98006 is still referenced (private 1,
> global
> 1)
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
> connection to server was lost
This bug can be closed. I was able to confirm that this bug has been
fixed by Tom's latest VACUUM fix. I was triggering this via a
pg_autovacuum that was running with a running with a 15sec sleep on a
schema load that was taking roughly 3 minutes (just the DDL). After
Tom's latest VACUUM commit, this bug does not appear to exist any more.
Thank you Tom! -sc
--
Sean Chittenden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Zhiltsov | 2004-10-05 07:47:57 | Re: Bug in PostrgeSQL 8.0beta |
| Previous Message | Sean Chittenden | 2004-10-04 23:57:20 | Re: Denial of service via VACUUM, all backends exit and restart... |