| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, 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-07 12:57:37 |
| Message-ID: | cef9be18-161c-98b9-ed0d-a23dc973df49@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021/07/07 18:09, Julien Rouhaud wrote:
> On Thu, Jul 1, 2021 at 4:28 PM Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> wrote:
>>
>> 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.
>
> It seems perfect, thanks!
Pushed. Thanks!
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2021-07-07 13:05:33 | Re: track_planning causing performance regression |
| Previous Message | Tatsuo Ishii | 2021-07-07 12:50:16 | Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors |