From: Bruce Momjian <pgman@candle.pha.pa.us>
To: me@shanewright.co.uk
Cc: pgsql-sql@postgresql.org
Subject: Re: table locking
Date: Mon, 18 Feb 2002 10:16:15 -0500 (EST)
Message-ID: <200202181516.g1IFGF517803@candle.pha.pa.us> (raw)
In-Reply-To: <200202181439.g1IEdDL16952@fullerruss.dsvr.co.uk>
Shane Wright wrote:
> Hi
>
> I'm having trouble getting my head round postgres's locking. I've read
> through all the docs but cant seem to find the right thingthat does what I
> want...
>
>
> Basically, there are a few tables in my system where a SELECT is done prior
> to an INSERT to avoid duplicating certain data and so forth.
>
> So, I want to lock the table for the transaction that does the stuff above so
> no more than one can run at a time (essentially making it SERIALIZABLE).
> But, I dont want to block other readers from SELECTing from the table at the
> same time...
>
> This is the classic multiple readers, single writer problem yes? I'm sure
> its doable, but I cant work out which locking / transaction isolation levels
> to use.
See my chapter on transactions. I think you want SERIALIZABLE
transaction mode.
http://www.postgresql.org/docs/awbook.html
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
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: pgman@candle.pha.pa.us, me@shanewright.co.uk
Subject: Re: table locking
In-Reply-To: <200202181516.g1IFGF517803@candle.pha.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