Jan Wieck wrote: > Tom Lane wrote: > > > [EMAIL PROTECTED] (Jan Wieck) writes: > >> Added GUC variable bgwriter_flush_method controlling the action > >> done by the background writer between writing dirty blocks and > >> napping. > > > >> none (default) no action > >> sync bgwriter calls smgrsync() causing a sync(2) > > > > Why would that be useful at all? I thought the purpose of the bgwriter > > was to avoid I/O storms, not provoke them. > > Calling sync(2) every time the background writer naps means calling it > every couple hundred milliseconds. That can hardly be called an IO > storm, it's more like a constant breeze.
I talked to Jan about the idea of sync on every background writer sleep. He is going to study the issue and report back. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
