From: | "William N(dot) Zanatta" <william(at)veritel(dot)com(dot)br> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: known bugs in sequences ? |
Date: | 2002-07-01 15:46:36 |
Message-ID: | 3D20795C.7070607@veritel.com.br |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Somebody called 'Tom Lane' tried to say something! Take a look:
> Henk Schets <henk(at)poppunt(dot)be> writes:
>
>>we just encountered this strange thing in our database. All our sequences were reset to 1. Is there any known bug that could be related to this ? Maybe with a jdbc driver or something ? We are using version 7.0.3.
>>It could very well be an exotic coding problem, but I want to be sure that it has nothing to do with our version of postgresql.
>
>
> All of your sequences at the same time? It's really hard to see how any
> internal bug in Postgres could cause that. They're not stored together,
> and there's no operation that visits them all. Sure you didn't have some
> client application run around and issue a lot of setvals?
>
> But having said that, 7.0.3 is verging on ancient history, and we are
> not fixing bugs in it anymore. I think you are well overdue for an
> update.
>
> regards, tom lane
>
Could this problem be related with CYCLE in SEQUENCEs creation?
William
--
Perl combines all of the worst aspects of BASIC, C and line noise.
-- Keith Packard
From | Date | Subject | |
---|---|---|---|
Next Message | Lamar Owen | 2002-07-01 16:36:56 | Re: (A) native Windows port |
Previous Message | Tom Lane | 2002-07-01 13:53:51 | Re: known bugs in sequences ? |