Re: BUG #5492: Query performs slowly and sequence corrupted

On Mon, Jun 7, 2010 at 5:36 PM, Piergiorgio Buongiovanni
<piergiorgio(dot)buongiovanni(at)netspa(dot)it> wrote:
> I reused the previous command to re-set the sequence value to the right one,
> but I see that the START value is now 59100. I reused the previous command
> another time and the START value is now 30440.
>
> I think this is a bug. I have a lot of problems with this sequence.

Sequences wouldn't directly affect retrieval times. But one way you
could get both of these symptoms is by having an application which
inserts many rows but aborts and rolls back the inserts without
committing. Perhaps a large copy which is interrupted. That would fill
the table with garbage dead records which could slow down retrieval
depending on the access method and also increase the sequence value.

You'll need to provide a lot more data before people would be able to
help you. I suggest you post the results of "explain analyze select
..." as well as some details of what previous operations you've done
on this database to pgsql-general(at)postgresql(dot)org(dot) pgsql-bugs is not
really appropriate unless you're reporting a specific problem with
postgresql in general, not an operational problem with your database.

--
greg