pgwin32_backend_usleep seems overly cute/confusing - Mailing list pgsql-hackers

From Tom Lane
Subject pgwin32_backend_usleep seems overly cute/confusing
Date
Msg-id 25201.1153015026@sss.pgh.pa.us
Whole thread Raw
List pgsql-hackers
Instead of this rigmarole with pg_usleep() being a macro to
pgwin32_backend_usleep, why don't we just call the function in
backend/port/win32/signal.c pg_usleep(), and put something like
#if defined(FRONTEND) || !defined(WIN32)

around the version in src/port/pgsleep.c?  We don't really want
that version present in the backend at all on Windows, ISTM.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Online index builds
Next
From: Tom Lane
Date:
Subject: Re: Forcing wal rotation