| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Track the amount of time waiting due to cost_delay |
| Date: | 2024-06-11 18:48:30 |
| Message-ID: | CA+Tgmoatdfycby69ZvAQkwa9RbKUebzqTe4W4_Eh53RN08nK_Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 11, 2024 at 2:47 PM Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
> I'm struggling to think of a scenario in which the number of waits would be
> useful, assuming you already know the amount of time spent waiting. Even
> if the number of waits is huge, it doesn't tell you much else AFAICT. I'd
> be much more likely to adjust the cost settings based on the percentage of
> time spent sleeping.
This is also how I see it.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Lakhin | 2024-06-11 19:00:01 | Re: Assertion failure in SnapBuildInitialSnapshot() |
| Previous Message | Nathan Bossart | 2024-06-11 18:47:29 | Re: Track the amount of time waiting due to cost_delay |