| From: | Matthew Wakeling <matthew(at)flymine(dot)org> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Proposal of tunable fix for scalability of 8.4 |
| Date: | 2009-03-18 11:49:33 |
| Message-ID: | alpine.DEB.2.00.0903181146030.21772@aragorn.flymine.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Wed, 18 Mar 2009, Heikki Linnakangas wrote:
> A linked list or an array of in-progress writes was my first thought as well.
> But the real problem is: how does the reader wait until all WAL up to X have
> been written? It could poll, but that's inefficient.
Good point - waiting for an exclusive lock on a page is a pretty easy way
to wake up at the right time.
However, is there not some way to wait for a notify? I'm no C expert, but
in Java that's one of the most fundamental features of a lock.
Matthew
--
A bus station is where buses stop.
A train station is where trains stop.
On my desk, I have a workstation.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2009-03-18 12:06:49 | Re: Proposal of tunable fix for scalability of 8.4 |
| Previous Message | Matthew Wakeling | 2009-03-18 11:45:47 | Re: Proposal of tunable fix for scalability of 8.4 |