Skip site navigation (1) Skip section navigation (2)

Re: PANIC caused by open_sync on Linux

From: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: Greg Smith <gsmith(at)gregsmith(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: PANIC caused by open_sync on Linux
Date: 2007-10-29 01:03:59
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Greg Smith <gsmith(at)gregsmith(dot)com> wrote:

> 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

I'd like to add:
- Remove "filling with zero" before we recycle WAL segments.

If it is not needed, we can avoid buffered i/o on open_sync except
first allocation of segments. I think we can do it if we have more
robust WAL records that can ignore garbage data written before.

ITAGAKI Takahiro
NTT Open Source Software Center

In response to


pgsql-hackers by date

Next:From: Merlin MoncureDate: 2007-10-29 01:18:04
Subject: Re: Proposal: real procedures again (8.4)
Previous:From: Tom LaneDate: 2007-10-28 23:56:29
Subject: Re: Backend misfeasance for DEFAULT NULL

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group