From: Florian Weimer <fw@deneb.enyo.de>
To: Martin Marques <martin@bugs.unl.edu.ar>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Rows with exclusive lock
Date: Sun, 23 Jul 2006 17:28:28 +0200
Message-ID: <87fygss5lv.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0607221151080.17932@bugs.unl.edu.ar>
References: <Pine.LNX.4.64.0607221135470.17932@bugs.unl.edu.ar>
<20060722144218.GH5125@surnet.cl>
<Pine.LNX.4.64.0607221151080.17932@bugs.unl.edu.ar>
* Martin Marques:
>> That's what SELECT FOR UPDATE does.
>
> Hi Alvaro,
>
> After the SELECT FOR UPDATE other transactions can still see the
> locked rows. I want a read/write lock, so no one can access does rows.
You should probably run the other transactions at SERIALIZABLE level.
I suppose this will make them wait for the completion of the update.
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: fw@deneb.enyo.de, martin@bugs.unl.edu.ar, alvherre@commandprompt.com
Subject: Re: Rows with exclusive lock
In-Reply-To: <87fygss5lv.fsf@mid.deneb.enyo.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