Message-ID: <4C80AF32.6000608@wp.pl>
Date: Fri, 03 Sep 2010 10:17:54 +0200
From: Ireneusz Pluta <ipluta@wp.pl>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: Alvaro Herrera <alvherre@alvh.no-ip.org>,
	Kevin Grittner <kevin.grittner@wicourts.gov>,
	"pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: Autovacuum and invalid page header
References: <4BEA8CD0.8070108@wp.pl>
 <4BEBC57002000025000316A3@gw.wicourts.gov>
	<1273811839-sup-7071@alvh.no-ip.org>
	<14800.1273812639@sss.pgh.pa.us>
In-Reply-To: <14800.1273812639@sss.pgh.pa.us>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Tom Lane pisze:
> Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
>   
>> Yeah, maybe we should make it put the failed table at the end of the
>> list, for the next run.  This is not simple to implement, if only
>> because autovac workers don't have any way to persist state from one run
>> to the next.  But this kind of thing causes enough problems that it's
>> probably worth it.
>>     
>
>   
>> One thing to keep in mind, though, is that a persistent error in a
>> single table is enough to keep a database's datfrozenxid from advancing,
>> and thus shut down in case the wraparound horizon comes too close.  So
>> perhaps what we need is more visibility into autovacuum problems.
>>     
>
> +1 for the latter.  A recurrent vacuum failure is something that needs
> to be dealt with ASAP, not partially-worked-around.
>
> 			regards, tom lane
>   
I am revisiting invalid page header cases due to my problem explained in 
another recent post from me.
I am not tracing development process too closely. But, as I can see the 
9.0 is almost out, let me ask here if this problem has been taken care of?