Postgres Pro
Downloads
Home   >   mailing lists

Re: LockAcquireExtended() dontWait vs weaker lock levels than already held - Mailing list pgsql-hackers

From Robert Haas
Subject Re: LockAcquireExtended() dontWait vs weaker lock levels than already held
Date
Msg-id CA+TgmoZNbDGwXMQfn8qK3FVu4Je81nHCF3UVAmDR8rM3yUp2EQ@mail.gmail.com
Whole thread Raw
In response to Re: LockAcquireExtended() dontWait vs weaker lock levels than already held  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Tree view 
On Tue, Mar 22, 2022 at 3:01 PM Andres Freund <andres@anarazel.de> wrote:
> We clearly already know how to compute whether a lock is "included" in
> something we already hold - after all ProcSleep() successfully does so.
>
> Isn't it a pretty trivial test? Seems like it'd boil down to something like

I don't mind you fixing the behavior. I just couldn't pass up an
opportunity to complain about the structure of lock.c.

-- 
Robert Haas
EDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [PATCH] Proof of concept for GUC improvements
Next
From: Alvaro Herrera
Date:
Subject: Re: Column Filtering in Logical Replication