Re: Maximum transaction rate

From: Ben Chobot <bench(at)silentmedia(dot)com>
To: Greg Smith <gsmith(at)gregsmith(dot)com>
Cc: 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:22:49
Message-ID: Pine.LNX.4.64.0903061320270.10022@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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....

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2009-03-06 21:39:09 Re: Maximum transaction rate
Previous Message Eric B. Ridge 2009-03-06 21:10:59 Re: set-valued function called in context that cannot accept a set