Re: track_planning causing performance regression - Mailing list pgsql-hackers

From Julien Rouhaud
Subject Re: track_planning causing performance regression
Date
Msg-id CAOBaU_ZxTGMapnWTCGaEiAHochUjzEB5XQN3hqbuf0xspDwSbg@mail.gmail.com
Whole thread Raw
In response to Re: track_planning causing performance regression  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Responses Re: track_planning causing performance regression  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List pgsql-hackers
On Thu, Jul 1, 2021 at 4:28 PM Fujii Masao <masao.fujii@oss.nttdata.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!



pgsql-hackers by date:

Previous
From: Andy Fan
Date:
Subject: Re: Keep notnullattrs in RelOptInfo (Was part of UniqueKey patch series)
Next
From: Julien Rouhaud
Date:
Subject: Re: Hook for extensible parsing.