| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | "Greg Smith" <greg(at)2ndquadrant(dot)com>, "Craig James" <craig_james(at)emolecules(dot)com>, "Matthew Wakeling" <matthew(at)flymine(dot)org>, <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Weird XFS WAL problem |
| Date: | 2010-06-03 19:17:28 |
| Message-ID: | 4C07B9780200002500031EBB@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> I think it's a case of the quickest, simplest answer to semi-new
> tech. Not sure what to do with barriers? Just flush the whole
> cache.
>
> I'm guessing that this will get optimized in the future.
Let's hope so.
That reminds me, the write barrier concept is at least on the
horizon as a viable technology; does anyone know if the asynchronous
graphs concept in this (one page) paper ever came to anything? (I
haven't hear anything about it lately.)
http://www.usenix.org/events/fast05/wips/burnett.pdf
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2010-06-03 19:31:22 | Re: Weird XFS WAL problem |
| Previous Message | Scott Marlowe | 2010-06-03 19:10:12 | Re: Weird XFS WAL problem |