From: Tom Lane <tgl@sss.pgh.pa.us>
To: Martin Langhoff (Catalyst IT) <martin@catalyst.net.nz>
Cc: PostgreSQL Bugs List <pgsql-bugs@postgresql.org>
Subject: Re: BUG #1083: Insert query reordering interacts badly with NEXTVAL()/CURRVAL()
Date: Tue, 24 Feb 2004 01:51:55 -0500
Message-ID: <18920.1077605515@sss.pgh.pa.us> (raw)
In-Reply-To: <403AF354.5030901@catalyst.net.nz>
References: <20040224012657.B86E5CF4A21@www.postgresql.com>
<18400.1077601067@sss.pgh.pa.us>
<403AF354.5030901@catalyst.net.nz>
"Martin Langhoff (Catalyst IT)" <martin@catalyst.net.nz> writes:
> Thanks for the clarification. I am curious, however: I can't find a
> means to achieve the same effect in a deterministic manner. Any pointers?
How about
SELECT nextval('seq'); -- ignore result
INSERT INTO ... VALUES (currval('seq'), currval('seq'));
regards, tom lane
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, martin@catalyst.net.nz, pgsql-bugs@postgresql.org
Subject: Re: BUG #1083: Insert query reordering interacts badly with NEXTVAL()/CURRVAL()
In-Reply-To: <18920.1077605515@sss.pgh.pa.us>
* 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