Re: Questions of 'for update'

Thanks so much.

I understand now.

Best Regards,
Zhenghua Lyu

On Mon, Jun 10, 2019 at 3:22 PM Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>
wrote:

> On Mon, Jun 10, 2019 at 12:42 PM Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
> wrote:
>
>> Hi,
>>
>> On Mon, Jun 10, 2019 at 3:50 PM Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>
>> wrote:
>> > On Mon, Jun 10, 2019 at 11:31 AM Zhenghua Lyu <zlv(at)pivotal(dot)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
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.enterprisedb.com&d=DwMFaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=4XHPyPZRSLhdU6MKCd2-Rw&m=xYe6nmboAo9yOHgVlKpvKmLcN1Re8JX2cSDYkaWtysM&s=nCk1b-WTJNHJJMWPzCsAKujWe0vV4wpRH4zpzMGutqc&e=>
>