Re: Dirty Buffer Writing [was Proposed LogWriter Scheme] - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Dirty Buffer Writing [was Proposed LogWriter Scheme]
Date
Msg-id 2036.1034088658@sss.pgh.pa.us
Whole thread Raw
In response to Re: Dirty Buffer Writing [was Proposed LogWriter Scheme]  ("Curtis Faith" <curtis@galtair.com>)
Responses Re: Dirty Buffer Writing [was Proposed LogWriter Scheme]  (Greg Copeland <greg@CopelandConsulting.Net>)
List pgsql-hackers
"Curtis Faith" <curtis@galtair.com> writes:
> Do you not think this is a potential performance problem to be explored?

I agree that there's a problem if the kernel runs short of buffer space.
I am not sure whether that's really an issue in practical situations,
nor whether we can do much about it at the application level if it is
--- but by all means look for solutions if you are concerned.

(This is, BTW, one of the reasons for discouraging people from pushing
Postgres' shared buffer cache up to a large fraction of total RAM;
starving the kernel of disk buffers is just plain not a good idea.)
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Analysis of ganged WAL writes
Next
From: Greg Copeland
Date:
Subject: Re: Dirty Buffer Writing [was Proposed LogWriter Scheme]