From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | gsmd(at)gmx-topmail(dot)de |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: sequences problem |
Date: | 2006-05-19 13:23:06 |
Message-ID: | 20060519132306.GE9080@surnet.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
gsmd(at)gmx-topmail(dot)de wrote:
> >Could you provide a complete test case?
> As I've been told, there is no special code, just a usual sequence
> usage. There is no small part of code that can be reproduced.
How do you use tose sequences?
> The situation is that there are 2 applications working with the same
> DB and accessing sequences. Each time application is started the
> sequences are reloaded (without doing this the sequences go crazy,
> e.g. you can get 1000 with 5 being the last value).
What do you mean by reloaded?
> > What's the output of
> > "SELECT * FROM sequence_name"?
> ERROR: relation "sequence_name" does not exist
Of course, you should have replaced "sequence_name" with the name of
your sequence.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-05-19 14:18:19 | Re: BUG #2443: 1 hour error at date calculation |
Previous Message | Jagadish Prasath Ramu | 2006-05-19 10:09:24 | BUG #2444: XA Connections given by posgres driver has auto-commit value false by default |