Re: PANIC caused by open_sync on Linux - Mailing list pgsql-hackers

From Greg Smith
Subject Re: PANIC caused by open_sync on Linux
Date
Msg-id Pine.GSO.4.64.0710262218020.28838@westnet.com
Whole thread Raw
In response to Re: PANIC caused by open_sync on Linux  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PANIC caused by open_sync on Linux
Re: PANIC caused by open_sync on Linux
List pgsql-hackers
On Fri, 26 Oct 2007, Tom Lane wrote:

>> The 8.3 bgwriter keeps running even during checkpoints, so it's feasible
>> to add such a feature now.
> I wonder though whether the walwriter wouldn't be a better place for it.

I do, too, but that wasn't available until too late in the 8.3 cycle to 
consider adding this feature to there either.

There's a couple of potential to-do list ideas that build on the changes 
in this area in 8.3:

-Aggressively pre-allocate WAL segments 
-Space out checkpoint fsync requests in addition to disk writes
-Consider re-inserting a smarter bgwriter all-scan that writes sorted by 
usage count during idle periods

--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Avoiding planning redundant backwards merges
Next
From: Camilo Porto
Date:
Subject: URGENT HELP about 'duration' stats