From: Florian Weimer <fweimer@bfk.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: INSERT/UPDATEs cycles and lack of phantom locking
Date: Wed, 19 Jul 2006 17:06:14 +0200
Message-ID: <827j291vo9.fsf@mid.bfk.de> (raw)
In-Reply-To: <25634.1153319178@sss.pgh.pa.us>
References: <82zmf60zf4.fsf@mid.bfk.de>
<25634.1153319178@sss.pgh.pa.us>
* Tom Lane:
> Why do you think that? If you're running in READ COMMITTED mode then
> each statement takes a new snapshot.
Ah, I should have explained that. I might need the SERIALIZABLE
isolation level in the future (this code doesn't need it, but other
things in the same transaction might require it).
In addition, it occurred to me that I get the INSERT failure only if
there is a suitable PRIMARY KEY/UNIQUE constraint on the table. I
haven't got that in all cases, so I need that advisory locking anyway,
I fear.
--
Florian Weimer <fweimer@bfk.de>
BFK edv-consulting GmbH http://www.bfk.de/
Durlacher Allee 47 tel: +49-721-96201-1
D-76131 Karlsruhe fax: +49-721-96201-99
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: fweimer@bfk.de, tgl@sss.pgh.pa.us
Subject: Re: INSERT/UPDATEs cycles and lack of phantom locking
In-Reply-To: <827j291vo9.fsf@mid.bfk.de>
* 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