|
19 | 19 | * |
20 | 20 | * |
21 | 21 | * IDENTIFICATION |
22 | | - * $PostgreSQL: pgsql/src/backend/postmaster/pgarch.c,v 1.10 2004/11/09 13:01:26 petere Exp $ |
| 22 | + * $PostgreSQL: pgsql/src/backend/postmaster/pgarch.c,v 1.11 2004/11/17 17:50:20 tgl Exp $ |
23 | 23 | * |
24 | 24 | *------------------------------------------------------------------------- |
25 | 25 | */ |
@@ -338,15 +338,14 @@ pgarch_MainLoop(void) |
338 | 338 |
|
339 | 339 | /* |
340 | 340 | * There shouldn't be anything for the archiver to do except to |
341 | | - * wait for a signal, so we could use pause(3) here... ...however, |
342 | | - * the archiver exists to protect our data, so she wakes up |
343 | | - * occasionally to allow herself to be proactive. In particular |
344 | | - * this avoids getting stuck if a signal arrives just before we |
345 | | - * enter sleep(). |
| 341 | + * wait for a signal, ... however, the archiver exists to |
| 342 | + * protect our data, so she wakes up occasionally to allow |
| 343 | + * herself to be proactive. In particular this avoids getting |
| 344 | + * stuck if a signal arrives just before we sleep. |
346 | 345 | */ |
347 | 346 | if (!wakened) |
348 | 347 | { |
349 | | -sleep(PGARCH_AUTOWAKE_INTERVAL); |
| 348 | +pg_usleep(PGARCH_AUTOWAKE_INTERVAL*1000000L); |
350 | 349 |
|
351 | 350 | curtime=time(NULL); |
352 | 351 | if ((unsignedint) (curtime-last_copy_time) >= |
|