Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #1276: Backend panics on SETVAL('..', 0)... - Mailing list pgsql-bugs

From Sean Chittenden
Subject Re: BUG #1276: Backend panics on SETVAL('..', 0)...
Date
Msg-id 676F5B32-1663-11D9-9F57-000A95C705DC@speakeasy.net
Whole thread Raw
In response to BUG #1276: Backend panics on SETVAL('..', 0)...  ("PostgreSQL Bugs List" <pgsql-bugs@postgresql.org>)
List pgsql-bugs
Tree view 
> 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

pgsql-bugs by date:

Previous
From: Sean Chittenden
Date:
Subject: Re: Denial of service via VACUUM, all backends exit and restart...
Next
From: "PostgreSQL Bugs List"
Date:
Subject: BUG #1279: pg_dump/resore has trouble with implicit sequences of renamed tables