| From: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
| Cc: | 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-21 13:55:16 |
| Message-ID: | 11FEF49E-80BB-4B74-996F-7FF14E63AF2D@yandex-team.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 19 Nov 2024, at 17:39, Greg Sabino Mullane <htamfids(at)gmail(dot)com> wrote:
>
> I'm curious what "using it wrong" means exactly?
Here's an example. pgSCV is querying pgss for every database separately every minute. It makes sense for the project. But when you have ~1000 databases, you have a lot of traffic to pgss alone. Even if you have only one active database, because all pgss results must be put into tuplestore before filtering. See [0] for details.
Best regards, Andrey Borodin.
[0] https://www.postgresql.org/message-id/flat/1AEEB240-9B68-44D5-8A29-8F9FDB22C801%40yandex-team.ru
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jian he | 2024-11-21 13:58:03 | Re: Proposal to use JSON for Postgres Parser format |
| Previous Message | Tom Lane | 2024-11-21 13:52:46 | Re: Planner picks n² query plan when available |