Re: track_planning causing performance regression

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, "Tharakan, Robins" <tharar(at)amazon(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: track_planning causing performance regression
Date: 2021-04-21 14:53:38
Message-ID: 20210421145338.GT7256@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 21, 2021 at 11:38:52PM +0900, Fujii Masao wrote:
> On 2021/04/19 23:55, Justin Pryzby wrote:
> > What does "kind" mean ? I think it means a "normalized" query or a "query
> > structure".
> >
> > "a fewer kinds" is wrong, so I think the docs should say "a small number of
> > queries" or maybe:
>
> Okay, I agree to update the description.
>
> > > > > Enabling this parameter may incur a noticeable performance penalty,
> > > > > especially similar queries are run by many concurrent connections and
> > > > > compete to update the same pg_stat_statements entry
>
> "a small number of" is better than "similar" at the above because
> "similar" sounds a bit unclear in this case?
>
> It's better to use "entries" rather than "entry" at the above?

How about like this?

Enabling this parameter may incur a noticeable performance penalty,
- especially when a fewer kinds of queries are executed on many
+ especially when queries with the same queryid are executed by many
concurrent connections.

Or:

Enabling this parameter may incur a noticeable performance penalty,
especially similar queries are executed by many concurrent connections
and compete to update a small number of pg_stat_statements entries.

--
Justin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2021-04-21 15:01:35 Re: TRUNCATE on foreign table
Previous Message Fujii Masao 2021-04-21 14:41:38 Re: TRUNCATE on foreign table