Horton

Re: Optimizing FastPathTransferRelationLocks()

Fujii Masao <masao.fujii@oss.nttdata.com>

View thread View on postgr.es
From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>, pgsql-hackers@lists.postgresql.org
Date: 2025-03-14T13:55:53Z
Lists: pgsql-hackers 

On 2025/03/13 0:32, Ashutosh Bapat wrote:
> Fair enough. The code is more readable this way. That itself is an improvement.
> 
> I stared at c4d5cb71d229095a39fda1121a75ee40e6069a2a to see whether
> there's any reason this was left aside at that time. I am convinced
> that it was just missed. I think this patch is good to be committed.

Thanks for reviewing the patch and confirming! I've pushed the patch.

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

Commits

  1. Optimize iteration over PGPROC for fast-path lock searches.

  2. Increase the number of fast-path lock slots