Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4VGgbE42186 for ; Thu, 31 May 2001 12:42:37 -0400 (EDT) (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.3/8.11.3) with ESMTP id f4VGgSR11130; Thu, 31 May 2001 12:42:29 -0400 (EDT) To: Brian Powell cc: pgsql-sql@postgresql.org Subject: Re: 7.1.1 Lock Problems on Views In-reply-to: <200105311532.JAA16968@sisyphus.owlscreech.com> References: <200105311532.JAA16968@sisyphus.owlscreech.com> Comments: In-reply-to Brian Powell message dated "Thu, 31 May 2001 09:33:11 -0600" Date: Thu, 31 May 2001 12:42:28 -0400 Message-ID: <11127.991327348@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200105/358 X-Sequence-Number: 3199 Brian Powell writes: > In our client app, we lock our table before doing something to it. Why don't you redesign the app to not use table-level locks? An MVCC-aware app should have little or no need for table-level locking. Locking views strikes me as a pretty fragile, if not outright broken, approach anyway --- a lock on a view would only protect you against other users of the same view, not against other users accessing the same underlying tables through different views. regards, tom lane