[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.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
