Re: track_planning causing performance regression

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, "Tharakan, Robins" <tharar(at)amazon(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: track_planning causing performance regression
Date: 2021-07-01 08:28:30
Message-ID: c162e1b3-08b0-2216-8e9e-80733d4a1a9b@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2021/06/30 0:12, Julien Rouhaud wrote:
>> Enabling this parameter may incur a noticeable performance penalty,
>> - especially when a fewer kinds of queries are executed on many
>> - concurrent connections.
>> + especially when queries with identical structure are executed by many
>> + concurrent connections which compete to update a small number of
>> + pg_stat_statements entries.
>>
>> It could say "identical structure" or "the same queryid" or "identical queryid".
>
> I think we should try to reuse the previous formulation. How about
> "statements with identical query structure"?

I'm fine with this. So what about the following diff? I added <structname> tag.

<varname>pg_stat_statements.track_planning</varname> controls whether
planning operations and duration are tracked by the module.
Enabling this parameter may incur a noticeable performance penalty,
- especially when a fewer kinds of queries are executed on many
- concurrent connections.
+ especially when statements with identical query structure are executed
+ by many concurrent connections which compete to update a small number of
+ <structname>pg_stat_statements</structname> entries.
The default value is <literal>off</literal>.
Only superusers can change this setting.

Regards,

--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2021-07-01 08:48:49 Re: ECPG bug fix: DECALRE STATEMENT and DEALLOCATE, DESCRIBE
Previous Message Masahiko Sawada 2021-07-01 07:53:42 Re: Skipping logical replication transactions on subscriber side