-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/2014 12:26 PM, Simon Riggs wrote:
> On 11 March 2014 03:41, Tom Lane wrote:
>> Joe Conway writes:
>>> I am probably missing something obvious, but why does the
>>> AccessShareLock remain held on a table after a SELECT statement
>>> is compl
On Tue, Mar 11, 2014 at 11:07 PM, Simon Riggs wrote:
> On 11 March 2014 17:29, Atri Sharma wrote:
> >
> >
> >
> > On Tue, Mar 11, 2014 at 10:56 PM, Simon Riggs
> wrote:
> >>
> >> On 11 March 2014 03:41, Tom Lane wrote:
> >> > Joe Conway writes:
> >> >> I am probably missing something obvious,
On 11 March 2014 17:29, Atri Sharma wrote:
>
>
>
> On Tue, Mar 11, 2014 at 10:56 PM, Simon Riggs wrote:
>>
>> On 11 March 2014 03:41, Tom Lane wrote:
>> > Joe Conway writes:
>> >> I am probably missing something obvious, but why does the
>> >> AccessShareLock remain held on a table after a SELE
On Tue, Mar 11, 2014 at 10:56 PM, Simon Riggs wrote:
> On 11 March 2014 03:41, Tom Lane wrote:
> > Joe Conway 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?
On 11 March 2014 03:41, Tom Lane wrote:
> Joe Conway 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 tran
Joe Conway 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 gener
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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? E.g.:
8<-
create table t1 ();
begin;
select * from t1;
select re
