Re: scalability bottlenecks with (many) partitions (and more)

Tomas Vondra <tomas@vondra.me>

From: Tomas Vondra <tomas@vondra.me>

To: Andres Freund <andres@anarazel.de>

Cc: Jakub Wartak <jakub.wartak@enterprisedb.com>, Robert Haas <robertmhaas@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-03-04T18:58:38Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Make FP_LOCK_SLOTS_PER_BACKEND look like a function
- c878de1db438 18.0 landed
Fix asserts in fast-path locking code
- a7e5237f268e 18.0 landed
Increase the number of fast-path lock slots
- c4d5cb71d229 18.0 landed

On 3/4/25 15:38, Tomas Vondra wrote:
> 
> ...
>
>>>
>>> Attached is a patch doing this, but considering it has nothing to do
>>> with the shmem sizing, I wonder if it's worth it.
>>
>> Yes.
>>
> 
> OK, barring objections I'll push the v2.
> 

Pushed, with the tweaks to use FastPathLockSlotsPerBackend() in a couple
more places.

I noticed sifaka started failing right after I pushed this:

https://buildfarm.postgresql.org/cgi-bin/show_history.pl?nm=sifaka&br=master

But I have no idea why would this cosmetic change cause issues with LDAP
tests, so I'm assuming the failure is unrelated, and the timing is
accidental and not caused by the patch.

regards

-- 
Tomas Vondra