Re: Sample rate added to pg_stat_statements - Mailing list pgsql-hackers

From Andrey M. Borodin
Subject Re: Sample rate added to pg_stat_statements
Date
Msg-id 11FEF49E-80BB-4B74-996F-7FF14E63AF2D@yandex-team.ru
Whole thread Raw
In response to Re: Sample rate added to pg_stat_statements  (Greg Sabino Mullane <htamfids@gmail.com>)
List pgsql-hackers

> On 19 Nov 2024, at 17:39, Greg Sabino Mullane <htamfids@gmail.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.
Butwhen you have ~1000 databases, you have a lot of traffic to pgss alone. Even if you have only one active database,
becauseall 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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Planner picks n² query plan when available
Next
From: jian he
Date:
Subject: Re: Proposal to use JSON for Postgres Parser format