Received: from sisyphus.owlscreech.com (owlscreech.com [207.174.31.35]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4VH50E53118 for ; Thu, 31 May 2001 13:05:00 -0400 (EDT) (envelope-from brian@owlscreech.com) Received: from cooper (server01.nicklebys.com [63.229.251.51]) by sisyphus.owlscreech.com (8.9.3/8.8.7) with ESMTP id LAA17208; Thu, 31 May 2001 11:04:59 -0600 Message-Id: <200105311704.LAA17208@sisyphus.owlscreech.com> Date: Thu, 31 May 2001 11:06:00 -0600 From: Brian Powell Content-Type: text/plain; format=flowed; charset=us-ascii Subject: Re: 7.1.1 Lock Problems on Views Cc: pgsql-sql@postgresql.org To: Tom Lane X-Mailer: Apple Mail (2.388) In-Reply-To: <11127.991327348@sss.pgh.pa.us> Mime-Version: 1.0 (Apple Message framework v388) Content-Transfer-Encoding: 7bit X-Archive-Number: 200105/359 X-Sequence-Number: 3200 On Thursday, May 31, 2001, at 10:42 AM, Tom Lane wrote: > 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. > Thanks, I'll read up on MVCC in the docs. While digging around, I came across the MVCC and it was the first I have heard of it (I haven't been reading up on the new features of 7.1)... --Brian