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-18 23:36:15
Message-ID: 20210418233615.GB7256@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Reviewing this change which was committed last year as
321fa6a4a26c9b649a0fbec9fc8b019f19e62289

On Fri, Jul 03, 2020 at 03:57:38PM +0900, Fujii Masao wrote:
> On 2020/07/03 13:05, Pavel Stehule wrote:
> > pá 3. 7. 2020 v 4:39 odesílatel Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> napsal:
> >
> > Maybe there can be documented so enabling this option can have a negative impact on performance.
>
> Yes. What about adding either of the followings into the doc?
>
> Enabling this parameter may incur a noticeable performance penalty.
>
> or
>
> Enabling this parameter may incur a noticeable performance penalty,
> especially when a fewer kinds of queries are executed on many
> concurrent connections.

Something seems is wrong with this sentence, and I'm not sure what it's trying
to say. Is this right ?

> Enabling this parameter may incur a noticeable performance penalty,
> especially when a small number of queries are executed on many
> concurrent connections.

--
Justin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2021-04-18 23:59:44 PG Docs - CREATE SUBSCRIPTION option list order
Previous Message Alvaro Herrera 2021-04-18 23:32:40 Re: pg_amcheck option to install extension