Re: Locking that will delayed a SELECT

--- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> A simple answer is to have T1 grab an ACCESS
> EXCLUSIVE lock on some
> table to block T2's progress. If that locks out
> third-party
> transactions that you'd rather would go through, you
> can probably use
> a lesser form of lock --- but then both T1 and T2
> will have to cooperate
> since each will need to explicitly take a lock.

- Is there a possibility of having a lock that
similar to a row level ACCESS EXCLUSIVE (i.e. ROW
ACCESS EXCLUSIVE lock) in the future release of
PostgreSQL? The ACCESS EXCLUSIVE lock also locks the
rows not used in T1, making concurrent transactions
almost impossible.

regards,
ludwig

__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com