Request a Demo
Home   >   mailing lists

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

From Hayato Kuroda (Fujitsu)
Subject RE: Using MyDatabaseId in SET_LOCKTAG_APPLY_TRANSACTION
Date
Msg-id OSCPR01MB149667693E4FBB661FC51A169F5D9A@OSCPR01MB14966.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: Using MyDatabaseId in SET_LOCKTAG_APPLY_TRANSACTION  (Maxim Orlov <orlovmg@gmail.com>)
List pgsql-hackers
Tree view 
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

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Support loser tree for k-way merge
Next
From: Chao Li
Date:
Subject: Re: Returning nbtree posting list TIDs in DESC order during backwards scans