| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>, Ilia Evdokimov <ilya(dot)evdokimov(at)tantorlabs(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Sample rate added to pg_stat_statements |
| Date: | 2024-11-20 15:59:12 |
| Message-ID: | CAKAnmmJ9dbO0Zka_UaMuAynHShagqTwisfnx+SDiwRbRjOK-cA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 19, 2024 at 5:07 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> One piece of it would be to see how much of such "bottlenecks" we
> would be able to get rid of by integrating pg_stat_statements into
> the central pgstats with the custom APIs, without pushing the module
> into core.
Any particular reason these days we cannot push this into core and allow
disabling on startup? To say this extension is widely used would be an
understatement.
Cheers,
Greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2024-11-20 16:33:39 | Re: sunsetting md5 password support |
| Previous Message | David G. Johnston | 2024-11-20 15:57:11 | Re: Document NULL |