| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Ben Chobot <bench(at)silentmedia(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Maximum transaction rate |
| Date: | 2009-03-13 18:43:30 |
| Message-ID: | 1236969810.7023.71.camel@jd-laptop.pragmaticzealot.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 2009-03-13 at 11:41 -0700, Ben Chobot wrote:
> On Fri, 13 Mar 2009, Joshua D. Drake wrote:
> Of course. But if you can't reliably flush the OS buffers (because, say,
> you're using LVM so fsync() doesn't work), then you can't say what
> actually has made it to the safety of the raid card.
Good point. So the next question of course is, does EVMS do it right?
This is actually a pretty significant issue.
Joshua D. Drake
>
--
PostgreSQL - XMPP: jdrake(at)jabber(dot)postgresql(dot)org
Consulting, Development, Support, Training
503-667-4564 - http://www.commandprompt.com/
The PostgreSQL Company, serving since 1997
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2009-03-13 18:59:56 | Re: Maximum transaction rate |
| Previous Message | Ben Chobot | 2009-03-13 18:41:53 | Re: Maximum transaction rate |