Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> ... It seems unlikely to cause any real
> problem if WAL writer takes a couple seconds to get with the program
> after a long period of inactivity; note that an async commit will kick
> it anyway, and a sync commit will probably half to flush WAL whether
> the WAL writer wakes up or not.

That's a good point.  What about only kicking the WAL writer in code
paths where a backend found itself having to write/flush WAL for itself?
The added overhead is very surely negligible in such a situation.

			regards, tom lane

In response to

• Re: Latch for the WAL writer - further reducing idle wake-ups. at 2012-05-03 00:41:29 from Robert Haas

Responses

• Re: Latch for the WAL writer - further reducing idle wake-ups. at 2012-05-03 04:11:48 from Robert Haas

pgsql-hackers by date

Next:	From: Vivek Singh Raghuwanshi	Date: 2012-05-03 04:00:27
	Subject: Re: [HACKERS] Features of Postgresql and Postgres-xc with MySQL
Previous:	From: Noah Misch	Date: 2012-05-03 01:06:48
	Subject: Re: Torn page hazard in ginRedoUpdateMetapage()