pg_sleep_enhancements.patch - Mailing list pgsql-hackers

From Pavel Stehule
Subject pg_sleep_enhancements.patch
Date
Msg-id CAFj8pRABP5EkzV1L099M6ujJTVo0k6_0RufXZ2p_Lnpt_Vm7Ug@mail.gmail.com
Whole thread Raw
Responses Re: pg_sleep_enhancements.patch
List pgsql-hackers
a) pg_sleep_for - no objection - it is simple and secure

b) pg_sleep_until

I am not sure - maybe this implementation is too simply. I see two possible risk where it should not work as users can expect

a) what will be expected behave whem time is changed - CET/CEST ?

b) what will be expected behave when board clock is not accurate and it is periodically fixed (by NTP) - isn't better to sleep only few seconds and recalculate sleeping interval?

Regards

Pavel

pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: FOREIGN KEY ... CONCURRENTLY
Next
From: Christian Kruse
Date:
Subject: Re: [PATCH] Use MAP_HUGETLB where supported (v3)