Re: Track the amount of time waiting due to cost_delay
От | Bertrand Drouvot |
---|---|
Тема | Re: Track the amount of time waiting due to cost_delay |
Дата | |
Msg-id | ZoI3rS2BdNi+kCWS@ip-10-97-1-34.eu-west-3.compute.internal обсуждение исходный текст |
Ответ на | Re: Track the amount of time waiting due to cost_delay ("Imseih (AWS), Sami" <simseih@amazon.com>) |
Список | pgsql-hackers |
Hi, On Fri, Jun 28, 2024 at 08:07:39PM +0000, Imseih (AWS), Sami wrote: > > 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. > > [1] https://www.postgresql.org/message-id/01000190606e3d2a-116ead16-84d2-4449-8d18-5053da66b1f4-000000%40email.amazonses.com > Yeah, I think it would make sense to put this thread on hold until we know more about [1] (you mentioned above) outcome. Regards, -- Bertrand Drouvot PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
В списке pgsql-hackers по дате отправления: