Re: [BUGS] BUG #2380: Sequence problem

2006-04-06 Thread Michael Fuhr
On Thu, Apr 06, 2006 at 10:04:03AM +, Alex Fomin wrote:
> While using the following function:
> ---
> nextval(sequence_name)  returns currval(sequence_name) -1
> ---
> while +1 is expected. It happens only sometimes, no dependency can be found.

Could you provide a complete test case?  That is, all SQL statements
that somebody could execute in an empty database to reproduce the
problem.  It doesn't have to be 100% reproducible as long as it
does exhibit the behavior every once in a while (an indication of
how often or under what circumstances, if known, would be helpful).

Is it possible that another session is altering the sequence to
start with a lower value?  Have you perchance set the sequence's
CACHE setting to a value other than 1 (one)?  What's the output of
"SELECT * FROM sequence_name"?  Are you making queries from more
than one session?  Are you using connection pooling?

-- 
Michael Fuhr

---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly


[BUGS] BUG #2380: Sequence problem

2006-04-06 Thread Alex Fomin

The following bug has been logged online:

Bug reference:  2380
Logged by:  Alex Fomin
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system:   Ubuntu Linux
Description:Sequence problem
Details: 

While using the following function:
---
nextval(sequence_name)  returns currval(sequence_name) -1
---
while +1 is expected. It happens only sometimes, no dependency can be found.

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster