Re: Why is AccessShareLock held until end of transaction? - Mailing list pgsql-hackers

From Atri Sharma
Subject Re: Why is AccessShareLock held until end of transaction?
Date
Msg-id CAOeZVicbGyCz5ASFoip+8OLAtn5zG+253wpyRt_JC9J=_5s+AA@mail.gmail.com
Whole thread Raw
In response to Re: Why is AccessShareLock held until end of transaction?  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Why is AccessShareLock held until end of transaction?  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers



On Tue, Mar 11, 2014 at 10:56 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
On 11 March 2014 03:41, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Joe Conway <mail@joeconway.com> writes:
>> I am probably missing something obvious, but why does the
>> AccessShareLock remain held on a table after a SELECT statement is
>> complete when in a transaction block?
>
> *Any* lock acquired by user command is held till end of transaction;
> AccessShareLock isn't special.
>
> In general, releasing early would increase the risk of undesirable
> behaviors such as tables changing definition mid-transaction.

I thought "good question" at first, but the workaround is simple...
just don't use multi-step transactions, submit each request as a
separate transaction.


Wouldnt that tend to get inefficient?

Regards,

Atri



--
Regards,
 
Atri
l'apprenant

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [PATCH] Store Extension Options
Next
From: Simon Riggs
Date:
Subject: Re: Why is AccessShareLock held until end of transaction?