Those are not feasible and efficient options. Lacking a better
solution, exposing a GUC that rarely needs tuning seems reasonable to me.
Anyway, hopefully the extra context is helpful! Please do share your
thoughts.
--
*Matt Smiley* | Staff Site Reliability Engineer at GitLab
Thank you Tomas! I really appreciate your willingness to dig in here and
help us out! The rest of my replies are inline below.
On Thu, Aug 3, 2023 at 1:39 PM Tomas Vondra
wrote:
> The analysis in the linked gitlab issue is pretty amazing. I wasn't
> planning to argue against the findings anywa
Hi Andres, thanks for helping! Great questions, replies are inline below.
On Sun, Aug 6, 2023 at 1:00 PM Andres Freund wrote:
> Hm, I'm curious whether you have a way to trigger the issue outside of your
> prod environment. Mainly because I'm wondering if you're potentially
> hitting
> the issu
>
> Why would the access frequency be uniform? In particular, there's a huge
> variability in how long the locks need to exist
>
As a supporting data point, our example production workload shows a 3x
difference between the most versus least frequently contended lock_manager
lock:
https://gitlab.co
