It occurred to me that if we elog(ERROR) during VACUUM, the vacuum
activity hint will not be reset. This will result in all subsequent I/O
by the current backend being treated by the bufmgr as though it resulted
from VACUUM. While elog(ERROR) during VACUUM is not a common occurrence,
I don't think it's wise to assume it is impossible.
Attached is a patch which resets the vacuum activity hint in
Barring any objections, I intend to apply this to REL8_0_STABLE and HEAD
sometime on Monday.
pgsql-patches by date
|Next:||From: Alvaro Herrera||Date: 2005-01-22 12:56:33|
|Subject: Re: vacuum hint on elog|
|Previous:||From: Neil Conway||Date: 2005-01-22 10:13:17|
|Subject: Re: pg_autovacuum/Win32 Fixes|