| 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 15:40:07 |
| Message-ID: | 20210421154007.GU7256@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 22, 2021 at 12:13:17AM +0900, Fujii Masao wrote:
> On 2021/04/21 23:53, Justin Pryzby wrote:
> > 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.
>
> I prefer this. But what about using "identical" instead of "similar"
> because pg_stat_statements docs already uses "identical" in some places?
I also missed "when", again...
> > Enabling this parameter may incur a noticeable performance penalty,
> > especially when queries with identical structure are executed by many concurrent connections
> > which compete to update a small number of pg_stat_statements entries.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Keller | 2021-04-21 16:01:04 | Re: ML-based indexing ("The Case for Learned Index Structures", a paper from Google) |
| Previous Message | Ian Zagorskikh | 2021-04-21 15:35:18 | Re: libpq compression |