Předmět: Re: unexpected rowlock mode when trigger is on the table
>
> CC:
>On 2019-Sep-05, Tomáš Záluský wrote:
>
>> Thanks for response.
>>
>> > I think there should be no overlap (PK is column "id", not modified)
>>
>> The update comman
On 2019-Sep-05, Tomáš Záluský wrote:
> Thanks for response.
>
> > I think there should be no overlap (PK is column "id", not modified)
>
> The update command sets the detail_id column which has unique constraint.
Oh, I see, yeah that explains it.
> What is unclear to me, why FOR NO KEY UPDATE
igger?
Tomáš
__
> Od: "Alvaro Herrera"
> Komu: "Tomáš Záluský"
> Datum: 05.09.2019 00:52
> Předmět: Re: unexpected rowlock mode when trigger is on the table
>
> CC:
>On 2019-Sep-03, Tomáš Záluský wrote:
>
>> postg
On 2019-Sep-03, Tomáš Záluský wrote:
> postgres=# begin;
> BEGIN
> postgres=# update master set detail_id=null, name='y' where id=1000;
> UPDATE 1
>
> In another psql console, I run:
>
> postgres=# select * from pgrowlocks('master');
> locked_row | locker | multi | xids | modes | pids
> ---
Hi pgsql hackers,
I'd like to ask you for kind advice with problem I'm pretty long stuck on. I
simplified it just to two tables and trigger. I described it thoroughly on
Stack Overflow a week ago but nobody responded so far, so I was advised by
Czech PG expert Pavel Stěhule to use this forum.
