Re: Use nanosleep(2) in pg_usleep, if available?

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org,Robert Haas <robertmhaas(at)gmail(dot)com>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Use nanosleep(2) in pg_usleep, if available?
Date: 2019-03-12 17:20:28
Message-ID: 5534A71E-1A0A-45D3-9A83-DFDC8DEBFCCC@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On March 12, 2019 10:17:19 AM PDT, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>On Tue, Mar 12, 2019 at 1:13 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> (I'm not sure what I think about which behavior is really more
>> desirable. We can debate that if there's actually a plausible
>> choice to be made, which seems to depend on Windows.)
>
>Yeah, that's a fair question. My motivation for asking was that I
>sometimes try to insert sleeps when debugging things, and they don't
>actually sleep, because they get interrupted. That's not dispositive,
>though.

Had that happen annoyingly often too. OTOH, we have some sleep loops where it's probably mildly helpful to react faster when an interrupt happens. But those probably should be rewritten to use latches.

Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Neel Patel 2019-03-12 17:34:17 Getting ERROR: bogus varno: 2
Previous Message Robert Haas 2019-03-12 17:17:19 Re: Use nanosleep(2) in pg_usleep, if available?