Re: [GENERAL] About upgrading a (tuple?) lock in a rollback'd sub-transaction - Mailing list pgsql-docs

From Amit Langote
Subject Re: [GENERAL] About upgrading a (tuple?) lock in a rollback'd sub-transaction
Date
Msg-id CA+HiwqH=y=eP+O-RiOzs0LtW8_ea26CSL0j_C0AJ-21vKi0qRA@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] About upgrading a (tuple?) lock in a rollback'd sub-transaction  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-docs
On Fri, Apr 11, 2014 at 11:52 AM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> Amit Langote wrote:
>> On Thu, Apr 10, 2014 at 10:25 PM, Rob Sargent <robjsargent@gmail.com> wrote:
>> > And it also tells you how to stop it --bibtex iirc
>>
>> Yeah, it's a caution against a potentially harmful usage anyway. Users
>> should not use it at all.
>>
>> I was just wondering if the description of the behavior, that is,
>> potential disappearance of certain locks is complete enough.
>
> You do realize that this is no longer the case in 9.3, right?
> I don't see a point in changing old releases' documentation.

I see, okay.
And yes, I'm aware that this's no longer an issue in 9.3.

Thanks,
Amit


pgsql-docs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [GENERAL] About upgrading a (tuple?) lock in a rollback'd sub-transaction
Next
From: Amit Langote
Date:
Subject: [doc] EXPLAIN CREATE MATERIALIZED VIEW AS?