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:34:13 -0500 (EST)
Message-ID: <200202181534.g1IFYDP19471@candle.pha.pa.us> (raw)
In-Reply-To: <200202181521.g1IFLwk24097@fullerruss.dsvr.co.uk>
Shane Wright wrote:
> Hi Bruce
>
> Thanks for the information (and the book link, straight in the bookmarks and
> remembered for an Amazon search...)
>
> Anyway, the chapter was helpful, but I'm still stuck. SERIALIZABLE looks
> like it would do the job, but I don't want any queries to fail/rollback - I'd
> rather they stalled on SET TRANSACTION or LOCK TABLE until the first was
> complete.
>
> Is this possible?
>
> I am also assuming that even with SERIALIZABLE, concurrent SELECTs can
> proceed unhindered?
Actually, I think the default READ COMMITTED will work fine for you.
Backends will block waiting for your write, then continue when you
commit, and reads will not be affected. I am not totally sure what you
are testing, so I suggest starting two psql sessions and trying it.
--
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: <200202181534.g1IFYDP19471@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