pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Brian Powell <brian@owlscreech.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: 7.1.1 Lock Problems on Views
Date: Thu, 31 May 2001 12:42:28 -0400
Message-ID: <11127.991327348@sss.pgh.pa.us> (raw)
In-Reply-To: <200105311532.JAA16968@sisyphus.owlscreech.com>
References: <200105311532.JAA16968@sisyphus.owlscreech.com>

Brian Powell <brian@owlscreech.com> 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



view thread (3+ messages)  latest in thread

Message-ID: <11127.991327348@sss.pgh.pa.us>
Permalink:  ../11127.991327348@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/11127.991327348@sss.pgh.pa.us

 · 

reply

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: tgl@sss.pgh.pa.us, brian@owlscreech.com
  Subject: Re: 7.1.1 Lock Problems on Views
  In-Reply-To: <11127.991327348@sss.pgh.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