Re: Why we are going to have to go DirectIO - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Why we are going to have to go DirectIO
Date
Msg-id 27536.1386102906@sss.pgh.pa.us
Whole thread Raw
In response to Re: Why we are going to have to go DirectIO  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
Responses Re: Why we are going to have to go DirectIO
List pgsql-hackers
Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes:
> If we care about our performance on various operating systems it is
> _OUR_ responsibility to track that closely and automated and report back
> and only if that feedback loop fails to work we are actually in a real
> position to consider something as drastical as considering a platform
> "undependable" or looking into alternatives (like directIO).

+1.  I fail to understand why anyone would think it's a good idea for us
to build our own I/O stack.  The resources that would be consumed by that
would probably be enough to sink the project, or at least ensure that we
made no progress on any other aspect of the system for a good long time.
(And I'm just talking development, never mind maintenance.)

Far better to invest some effort in providing decent feedback to the
platforms we depend on.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: logical changeset generation v6.7
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Fix a couple of bugs in MultiXactId freezing