| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Rob Sargent <robjsargent(at)gmail(dot)com> |
| Cc: | 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 00:45:52 |
| Message-ID: | CA+HiwqH6gWisL=PK2EKvOO2RkGXoCo+nAqpMn5YGW8gnKiwg6g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-general |
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.
--
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-04-11 02:52:47 | Re: [GENERAL] About upgrading a (tuple?) lock in a rollback'd sub-transaction |
| Previous Message | Bruce Momjian | 2014-04-11 00:02:33 | Re: Upgrading doc does not mention pg_restore at all |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-04-11 02:52:47 | Re: [GENERAL] About upgrading a (tuple?) lock in a rollback'd sub-transaction |
| Previous Message | Haribabu Kommi | 2014-04-11 00:28:08 | Re: HOT standby on windows not working |