pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Simeo Reig <simreig@terra.es>
To: Justin Clift <justin@postgresql.org>
To: Keary Suska <hierophant@pcisys.net>
Cc: Postgres-PHP <pgsql-php@postgresql.org>
Subject: Re: Nextval Problems
Date: Thu, 22 Aug 2002 21:58:07 +0200
Message-ID: <002901c24a16$3c05bc60$0a00a8c0@win2000> (raw)
References: <B989CD84.1239E%hierophant@pcisys.net>
	<3D64DC8B.CCA7D984@postgresql.org>

curval() or currval() can't remember

Best Regards
Simeo Reig

----- Original Message -----
From: "Justin Clift" <justin@postgresql.org>
To: "Keary Suska" <hierophant@pcisys.net>
Cc: "Postgres-PHP" <pgsql-php@postgresql.org>
Sent: Thursday, August 22, 2002 2:43 PM
Subject: Re: [PHP] Nextval Problems


> Hi Keary,
>
> Keary Suska wrote:
> <snip>
> > So--I don't see much wrong. If you make the changes I recommend, and you
are
> > still experiencing the problem, there is still something wrong with your
> > code. Probably in the parts you don't show us.
>
> Once had a *weird* problem with PG 7.0.? whereby it was incrementing by
> 2 for every invocation of nextval(), even though I was the only client -
> a single connection with psql - and the increment value of the sequence
> was definitely 1.
>
> Can't remember how I fixed it for sure, but think it was something along
> the lines of dropping the sequence and creating it again (manually).
> Have a feeling that many triggers or constraints turned out to be
> involved, but can't remember for sure.
>
> Definitely don't think this is a common occurance though.
>
> Regards and best wishes,
>
> Justin Clift
>
>
> > Keary Suska
> > Esoteritech, Inc.
> > "Leveraging Open Source for a better Internet"
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 4: Don't 'kill -9' the postmaster
>
> --
> "My grandfather once told me that there are two kinds of people: those
> who work and those who take the credit. He told me to try to be in the
> first group; there was less competition there."
>    - Indira Gandhi
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>




view thread (7+ messages)

Message-ID: <002901c24a16$3c05bc60$0a00a8c0@win2000>
Permalink:  ../002901c24a16$3c05bc60$0a00a8c0@win2000/
Also on:    postgresql.org/message-id/002901c24a16$3c05bc60$0a00a8c0@win2000

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: simreig@terra.es, justin@postgresql.org, hierophant@pcisys.net
  Subject: Re: Nextval Problems
  In-Reply-To: <002901c24a16$3c05bc60$0a00a8c0@win2000>
  References: <B989CD84.1239E%hierophant@pcisys.net> <3D64DC8B.CCA7D984@postgresql.org> <002901c24a16$3c05bc60$0a00a8c0@win2000>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox