Re: pg_arch.c call to sleep() - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: pg_arch.c call to sleep()
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCE4760DE@algol.sollentuna.se
Whole thread Raw
In response to pg_arch.c call to sleep()  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
> > We have the following warning on Windows:
> > pgarch.c:349: warning: implicit declaration of function `sleep'
>
> > To fix it we could include the right header (which appears to be
> > <stdlib.h> in the Windows/Mingw case), or we could replace
> the call by
> > a call to pg_usleep().
>
> <stdlib.h> is included automatically by c.h, so that surely
> won't fix it.
>
> I have some recollection that we invented pg_usleep in part
> because we wanted to not use sleep() at all in the backend,
> but I don't recall why (and the reasoning might not apply to
> the archiver process, anyway).

win32 signal handling won't interrupt sleep(), just pg_usleep().

//Magnus


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: CREATE TYPE with two args
Next
From: "Katsaros Kwn/nos"
Date:
Subject: Re: Memory Context problems...