RE: Using MyDatabaseId in SET_LOCKTAG_APPLY_TRANSACTION

From: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
To: 'Maxim Orlov' <orlovmg(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: RE: Using MyDatabaseId in SET_LOCKTAG_APPLY_TRANSACTION
Date: 2025-12-03 12:27:06
Message-ID: OSCPR01MB149667693E4FBB661FC51A169F5D9A@OSCPR01MB14966.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

[1]: https://www.postgresql.org/message-id/TYAPR01MB5866E4B208BFAAA5A05B1EECF53F9%40TYAPR01MB5866.jpnprd01.prod.outlook.com

Best regards,
Hayato Kuroda
FUJITSU LIMITED

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2025-12-03 12:31:43 Re: Returning nbtree posting list TIDs in DESC order during backwards scans
Previous Message Heikki Linnakangas 2025-12-03 12:23:53 Re: Support loser tree for k-way merge