Re: Maximum transaction rate - Mailing list pgsql-general

From Tom Lane
Subject Re: Maximum transaction rate
Date
Msg-id 5459.1236961423@sss.pgh.pa.us
Whole thread Raw
In response to Re: Maximum transaction rate  (Marco Colombo <pgsql@esiway.net>)
Responses Re: Maximum transaction rate
List pgsql-general
Marco Colombo <pgsql@esiway.net> writes:
> And I'm still wondering. The problem with LVM, AFAIK, is missing support
> for write barriers. Once you disable the write-back cache on the disk,
> you no longer need write barriers. So I'm missing something, what else
> does LVM do to break fsync()?

I think you're imagining that the disk hardware is the only source of
write reordering, which isn't the case ... various layers in the kernel
can reorder operations before they get sent to the disk.

            regards, tom lane

pgsql-general by date:

Previous
From: Alan Hodgson
Date:
Subject: Re: postmaster hangs on delete from
Next
From: Tomasz Olszak
Date:
Subject: Problem with accesing Oracle from plperlu function when using remote pg client client.