From: | Sami Imseih <samimseih(at)gmail(dot)com> |
---|---|
To: | Ilia Evdokimov <ilya(dot)evdokimov(at)tantorlabs(dot)com> |
Cc: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Alena Rybakina <a(dot)rybakina(at)postgrespro(dot)ru>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Greg Sabino Mullane <htamfids(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Sample rate added to pg_stat_statements |
Date: | 2025-01-29 21:55:00 |
Message-ID: | CAA5RZ0uKAm0sxcU40R+G9mb8g=jBC5bmj4zLmSyTz40vJEF3SA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> and we've been trying to solve a non-existent problem?
Anecdotally speaking, Most users will encounter bottlenecks
due to exclusive locks on pgss hash ( dealloc and garbage collection )
more often than they will on the spinlock. The spinlock will likely
become more of an issue when you are not seeing much dealloc/gc
and running on a very large machine. So, I don't think it's a non-existent
problem, but I don't think it's the most common problem.
Regards,
Sami
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Smith | 2025-01-29 23:15:47 | Re: Pgoutput not capturing the generated columns |
Previous Message | Masahiko Sawada | 2025-01-29 21:47:08 | pg_rewind with --write-recovery-conf option doesn't write dbname to primary_conninfo value. |