From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: literature on write-ahead logging |
Date: | 2011-06-09 04:40:12 |
Message-ID: | BANLkTi=SuaiXtBrm93cYmAjLEjLG7CsT=Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jun 8, 2011 at 11:24 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> I did a brief literature search for papers on breaking the
> WAL-serialization bottleneck today and hit upon this:
>
> Aether: A Scalable Approach to Logging, Ryan Johnson, Ippokratis Pandis, et al.
> http://infoscience.epfl.ch/record/149436/files/vldb10aether.pdf
>
> Section 5 appears to be the most relevant to our problems with WALInsertLock.
>
> They reject the approach that I proposed, wherein WAL is generated by
> individual backends in their own queues and serialized later: "While a
> total ordering is not technically required for correctness, valid
> partial orders tend to be too complex and interdependent to be worth
> pursuing as a performance optimization"; see also appendix A.5, which
> may be succinctly summarized as "no one does that".
heh -- makes total sense. great stuff.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Brar Piening | 2011-06-09 05:33:06 | Re: smallserial / serial2 |
Previous Message | Jeevan Chalke | 2011-06-09 04:39:36 | Re: Invalid byte sequence for encoding "UTF8", caused due to non wide-char-aware downcase_truncate_identifier() function on WINDOWS |