From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Sergey Sergey <ioxgrey(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] fastpacth-locks compile time options |
Date: | 2023-09-18 23:52:35 |
Message-ID: | ZQjiwxMf9ug9tbQ6@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Sep 18, 2023 at 05:49:51PM +0300, Sergey Sergey wrote:
> Hope this patch will be usefull/
- uint64 fpLockBits; /* lock modes held for each fast-path slot */
+ uint8 fpLockBits[FP_LOCK_SLOTS_PER_BACKEND]; /* lock modes
If my maths are right, this makes PGPROC 8 bytes larger with 16 slots
by default. That is not a good idea.
+ --runstatedir=DIR modifiable per-process data [LOCALSTATEDIR/run]
And this points out that ./configure has been generated with one of
Debian's autoreconf commands, which is something to avoid.
I am not sure that this patch is a good idea long-term. Wouldn't it
be better to invent new and more scalable concepts able to tackle
bottlenecks around these code paths instead of using compile-time
tweaks like that?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2023-09-18 23:58:47 | Re: Optimizing "boundary cases" during backward scan B-Tree index descents |
Previous Message | Michael Paquier | 2023-09-18 23:45:52 | Re: dikkop seems unhappy because of openssl stuff (FreeBSD 14-BETA1) |