Re: scalability bottlenecks with (many) partitions (and more)
Tomas Vondra <tomas@vondra.me>
From: Tomas Vondra <tomas@vondra.me>
To: Jakub Wartak <jakub.wartak@enterprisedb.com>
Cc: Robert Haas <robertmhaas@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
Andres Freund <andres@anarazel.de>
Date: 2024-09-21T18:33:49Z
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
Hi, I've finally pushed this, after many rounds of careful testing to ensure no regressions, and polishing. All changes since the version shared on September 13 are only cosmetic - renaming a macro to keep it consistent with the other ones, clarifying a couple comments etc. Nothing major. I ended up squashing the two parts into a single commit. I thought about keeping the two steps, but it seemed pointless - the first part inflated the PGPROC struct, which I didn't like to commit, even if only as an intermediate WIP state. So far buildfarm didn't blew up, so let's hope it will stay that way. I just realized there's no CF entry for this - sorry about that :-( I started the thread a year ago to discuss an experimental patche, and it never made it to CFA. But there was a discussion spanning a year, so hopefully that's enough. regards -- Tomas Vondra