Skip site navigation (1) Skip section navigation (2)

BUG #5476: sequence corruption

From: "Piergiorgio Buongiovanni" <p(dot)buongiovanni(at)net-international(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #5476: sequence corruption
Date: 2010-05-27 09:10:20
Message-ID: 201005270910.o4R9AKDd038676@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      5476
Logged by:          Piergiorgio Buongiovanni
Email address:      p(dot)buongiovanni(at)net-international(dot)com
PostgreSQL version: 8.3.4
Operating system:   CentOS (Redhat 5.4)
Description:        sequence corruption
Details: 

We experimented a sequence corruption on a table:
If we now look at the sequence data using pgAdmin version 1.8.4, we see the
following:

CREATE SEQUENCE business.subject_isid_seq
  INCREMENT 1
  MINVALUE 1
  MAXVALUE 9223372036854775807
  START 58827944
  CACHE 1;
ALTER TABLE business.subject_isid_seq OWNER TO netdw_owner;

The problem is that now the search on the table business.Subject (where the
sequence is used) performs very slowly. It seems the data are corrupted but
at the end I can see that there is a record created with the number 463663
instead of 57. As you can see the next value will be used is 58827944.
Which is the problem? Can I recover this situation and restore the right
sequence value? I tried to set the START value to 58 but, as you can see,
the value changed.

Responses

pgsql-bugs by date

Next:From: Boszormenyi ZoltanDate: 2010-05-27 11:34:40
Subject: Re: Cache lookup failure for index during pg_dump
Previous:From: Jasen BettsDate: 2010-05-27 07:56:16
Subject: Re: BUG #5469: regexp_matches() has poor behaviour and more poor documentation

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group