Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g1IFhBE00902 for ; Mon, 18 Feb 2002 10:43:12 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g1IFguS11228; Mon, 18 Feb 2002 10:42:56 -0500 (EST) To: me@shanewright.co.uk cc: Bruce Momjian , pgsql-sql@postgresql.org Subject: Re: table locking In-reply-to: <200202181521.g1IFLwk24097@fullerruss.dsvr.co.uk> References: <200202181516.g1IFGF517803@candle.pha.pa.us> <200202181521.g1IFLwk24097@fullerruss.dsvr.co.uk> Comments: In-reply-to Shane Wright message dated "Mon, 18 Feb 2002 15:22:11 +0000" Date: Mon, 18 Feb 2002 10:42:56 -0500 Message-ID: <11225.1014046976@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200202/215 X-Sequence-Number: 6639 I think you want just LOCK TABLE tab IN SHARE ROW EXCLUSIVE MODE or LOCK TABLE tab IN EXCLUSIVE MODE. The latter would lock out SELECT FOR UPDATE, the former wouldn't. regards, tom lane