| From: | Sergei Kornilov <sk(at)zsrv(dot)org> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Masahiro Ikeda <ikedamsh(at)oss(dot)nttdata(dot)com>, "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
| Subject: | Re: Track the amount of time waiting due to cost_delay |
| Date: | 2024-12-14 09:39:23 |
| Message-ID: | 1983281734169163@sjg23nxaikj7vz54.iva.yp-c.yandex.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi
+ Only superusers and users with the appropriate <literal>SET</literal>
+ privilege and change this setting.
a typo? should be "can change"?
I like the separation of vacuum_delay_point and analyze_delay_point, it improves the readability of the analyze code. Looks good. I would like to enable track_cost_delay_timing by default, but the analogy with track_io_timing is good... I agree that it is better to have it off by default.
regards, Sergeii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ryo Kanbayashi | 2024-12-14 11:42:01 | Re: typo in a comment of restrictinfo.c |
| Previous Message | Thomas Munro | 2024-12-14 09:26:37 | Re: FileFallocate misbehaving on XFS |