Request a Demo
Home   >   mailing lists

Re: Using MyDatabaseId in SET_LOCKTAG_APPLY_TRANSACTION - Mailing list pgsql-hackers

From Maxim Orlov
Subject Re: Using MyDatabaseId in SET_LOCKTAG_APPLY_TRANSACTION
Date
Msg-id CACG=ezasdryCbzaW1Kg+ecskg2o+QGurbbWKG4yN1054BBy4BQ@mail.gmail.com
Whole thread Raw
In response to RE: Using MyDatabaseId in SET_LOCKTAG_APPLY_TRANSACTION  ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>)
List pgsql-hackers
Tree view

On Wed, 3 Dec 2025 at 15:27, Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com> wrote:
Dear Maxim,

I recalled my post [1]. The database id is helpful when we output lock
information by DescribeLockTag(). Since it would be called when the system might
be under the deadlock, any locks should not be acquired even AccessShare. It can
be done if catcache is missed.

OK, now I get it. Thank you very much for the explanation.

--
Best regards,
Maxim Orlov.

pgsql-hackers by date:

Previous
From: "Yilin Zhang"
Date:
Subject: Re:Re: pg_recvlogical: Prevent flushed data from being re-sent after restarting replication
Next
From: Maxim Orlov
Date:
Subject: Re: POC: make mxidoff 64 bits