| From: | Larry Rosenman <ler(at)lerctr(dot)org> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WAL fsync scheduling |
| Date: | 2000-11-18 15:36:49 |
| Message-ID: | 20001118093649.A6714@lerami.lerctr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> [001117 23:21]:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Other backend will see they are not the lowest
> > WAIT_ON_FSYNC and will wait for their byte to be set to NOT_IN_COMMIT
> > so they can then continue, knowing their data was synced.
>
> How will they wait? Without a semaphore involved, your answer must
> be either "timed sleep" or "busy-wait loop", neither of which is
> attractive ...
how about sigpause, and using SIGUSR1/SIGUSR2 to wake them up ?
>
> regards, tom lane
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 (voice) Internet: ler(at)lerctr(dot)org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-11-18 17:43:40 | Re: WAL fsync scheduling |
| Previous Message | Bruce Momjian | 2000-11-18 14:32:17 | Re: location of Unix socket |