| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(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:13:17 |
| Message-ID: | f2aa2d6a-3b78-0526-4ca5-8ace10eb745e@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2021-04-21 15:21:31 | decoupling table and index vacuum |
| Previous Message | Magnus Hagander | 2021-04-21 15:04:42 | Re: RFE: Make statistics robust for unplanned events |