| From: | "Imseih (AWS), Sami" <simseih(at)amazon(dot)com> |
|---|---|
| To: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: Track the amount of time waiting due to cost_delay |
| Date: | 2024-06-28 20:07:39 |
| Message-ID: | 8D4DC535-1C51-44A9-ABDD-420F975AE8A9@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 46ebdfe164 will interrupt the leaders sleep every time a parallel workers reports
> progress, and we currently don't handle interrupts by restarting the sleep with
> the remaining time. nanosleep does provide the ability to restart with the remaining
> time [1], but I don't think it's worth the effort to ensure more accurate
> vacuum delays for the leader process.
After discussing offline with Bertrand, it may be better to have
a solution to deal with the interrupts and allows the sleep to continue to
completion. This will simplify this patch and will be useful
for other cases in which parallel workers need to send a message
to the leader. This is the thread [1] for that discussion.
Regards,
Sami
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-06-28 20:29:14 | Re: Restart pg_usleep when interrupted |
| Previous Message | Imseih (AWS), Sami | 2024-06-28 19:59:15 | Restart pg_usleep when interrupted |