Re: Bug with sequence ?

Well correcting the report:

by the past, i was used to have this trouble ( using 7.2b5 or prior and
ipchains)

the only 2 occurences i have now in my log are not linked to sequence so it
must occur sometime somehow but it has nothing to do with postgres.

However by the past, i had this trouble with sequence, i dont know if i get
rid off this issue updating to 7.2RC2 or moving to IPTABLE instead of
ipchains.

----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Christian Meunier" <vchris(at)club-internet(dot)fr>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Sent: Monday, February 04, 2002 5:21 PM
Subject: Re: [HACKERS] Bug with sequence ?

> "Christian Meunier" <vchris(at)club-internet(dot)fr> writes:
> > When i insert a new tuple i use: insert into test
values(nextval('test_num_=
> > seq'),......);
> > When i look at my postgres log, time to time i see:
> > 2002-02-04 08:11:47 ERROR: Cannot insert a duplicate key into unique
index=
> > test_pkey
>
> You sure that's the *only* way that the num column gets inserted or
> updated?
>
> regards, tom lane
>