| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Ben Chobot <bench(at)silentmedia(dot)com> |
| Cc: | Greg Smith <gsmith(at)gregsmith(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jack Orenstein <jack(dot)orenstein(at)hds(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Maximum transaction rate |
| Date: | 2009-03-06 21:39:09 |
| Message-ID: | dcc563d10903061339y51475826p10675155a7fc0dc3@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Mar 6, 2009 at 2:22 PM, Ben Chobot <bench(at)silentmedia(dot)com> wrote:
> On Fri, 6 Mar 2009, Greg Smith wrote:
>
>> On Fri, 6 Mar 2009, Tom Lane wrote:
>>
>>> Otherwise you need to reconfigure your drive to not cache writes.
>>> I forget the incantation for that but it's in the PG list archives.
>>
>> There's a dicussion of this in the docs now,
>> http://www.postgresql.org/docs/8.3/interactive/wal-reliability.html
>
> How does turning off write caching on the disk stop the problem with LVM? It
> still seems like you have to get the data out of the OS buffer, and if
> fsync() doesn't do that for you....
I think he was saying otherwise (if you're not using LVM and you still
have this super high transaction rate) you'll need to turn off the
drive's write caches. I kinda wondered at it for a second too.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2009-03-06 21:51:45 | Re: iSCSI SAN Suggestions |
| Previous Message | Ben Chobot | 2009-03-06 21:22:49 | Re: Maximum transaction rate |