pgwin32_backend_usleep seems overly cute/confusing

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: pgwin32_backend_usleep seems overly cute/confusing
Date: 2006-07-16 01:57:06
Message-ID: 25201.1153015026@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-07-16 02:24:01 Re: Forcing wal rotation
Previous Message Joshua D. Drake 2006-07-16 01:37:58 Re: Online index builds