| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Rob Sargent <robjsargent(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org>, "pgsql-docs(at)postgresql(dot)org" <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] About upgrading a (tuple?) lock in a rollback'd sub-transaction |
| Date: | 2014-04-11 03:40:53 |
| Message-ID: | CA+HiwqH=y=eP+O-RiOzs0LtW8_ea26CSL0j_C0AJ-21vKi0qRA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-general |
On Fri, Apr 11, 2014 at 11:52 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Amit Langote wrote:
>> On Thu, Apr 10, 2014 at 10:25 PM, Rob Sargent <robjsargent(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | rudolf | 2014-04-13 09:36:08 | documentation: json processing table pasto |
| Previous Message | Alvaro Herrera | 2014-04-11 02:52:47 | Re: [GENERAL] About upgrading a (tuple?) lock in a rollback'd sub-transaction |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Venkata Balaji Nagothi | 2014-04-11 04:35:00 | Re: postgresql.conf question... CPU spikes |
| Previous Message | Alvaro Herrera | 2014-04-11 02:52:47 | Re: [GENERAL] About upgrading a (tuple?) lock in a rollback'd sub-transaction |