Postgres Pro
Downloads
Home   >   mailing lists

Re: Questions of 'for update' - Mailing list pgsql-hackers

From Kuntal Ghosh
Subject Re: Questions of 'for update'
Date
Msg-id CAGz5QCL6U+3k=1iDcQcEjb-j960h0GRVcBJM-_f27WH7EJU3-Q@mail.gmail.com
Whole thread Raw
In response to Re: Questions of 'for update'  (Etsuro Fujita <etsuro.fujita@gmail.com>)
Responses Re: Questions of 'for update'
List pgsql-hackers
Tree view
On Mon, Jun 10, 2019 at 12:42 PM Etsuro Fujita <etsuro.fujita@gmail.com> wrote:
Hi,

On Mon, Jun 10, 2019 at 3:50 PM Kuntal Ghosh <kuntalghosh.2007@gmail.com> wrote:
> On Mon, Jun 10, 2019 at 11:31 AM Zhenghua Lyu <zlv@pivotal.io> wrote:
>> 2. Is the case above a bug or a feature?
>>
> IMHO, it looks like an expected behaviour of a correct transaction management implementation.

This is documented behavior; see the Caution for The Locking Clause on
the SELECT reference page:
https://www.postgresql.org/docs/11/sql-select.html


Great. It also suggests a workaround. 


--
Thanks & Regards,
Kuntal Ghosh
EnterpriseDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: Questions of 'for update'
Next
From: Kuntal Ghosh
Date:
Subject: Re: Why to index a "Recently DEAD" tuple when creating index