DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=ymail.com;
	h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=6MBtTO0v2dqYaIeLVjJs9Z+aaLelrHzTi0bkUDSIv9zE3zfGujPk02jxl4usKi3cWpf0vDNABa06hJO0LqH08+fujSEgR5CCUP0t99QPKvd2+JPORCV7I0sep0DvP65t+OJJxqRSIRFLUEiE0nHX/RCca/aLmWwSszUj1JQvs9Q=;
References: 
 <CAB9893het38CbHoHOt=GZ5tuUnb77EauGidjHsyy7Mqu_4_P9w@mail.gmail.com>
	<28473.1365724754@sss.pgh.pa.us>
	<1365731282.15026.YahooMailNeo@web162905.mail.bf1.yahoo.com>
	<CAOR=d=2sAp5YwXQ6i5361jNeh51jqtg-2GYUJe6bgeT2Y_+QxA@mail.gmail.com>
Message-ID: <1365780972.41333.YahooMailNeo@web162906.mail.bf1.yahoo.com>
Date: Fri, 12 Apr 2013 08:36:12 -0700 (PDT)
From: Kevin Grittner <kgrittn@ymail.com>
Reply-To: Kevin Grittner <kgrittn@ymail.com>
Subject: Re: after 9.2.4 patch vacuumdb -avz not analyzing all tables
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Mike Broers <mbroers@gmail.com>,
	"pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>,
	"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>,
	Jan Wieck <JanWieck@yahoo.com>
In-Reply-To: 
 <CAOR=d=2sAp5YwXQ6i5361jNeh51jqtg-2GYUJe6bgeT2Y_+QxA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Scott Marlowe <scott.marlowe@gmail.com> wrote:

> Does this behavior only affect the 9.2 branch? Or was it ported
> to 9.1 or 9.0 or 8.4 as well?

After leaving it on master for a while to see if anyone reported
problems in development, I back-patched as far as 9.0 in time for
the 9.2.3 (and related) patches.=A0 Prior to that the code was too
different for it to be the same patch, and (perhaps not entirely
coincidentally) I had not seen the problems before 9.0.=A0 From 9.0
on I have seen multiple sites (all using queuing from Slony or a
JMS implementation) with recurring problems when the queue
temporarily got large, shrank again, and then wrapped around to the
beginning of the table's file space.=A0 In some cases performance was
so impaired that when such an event was triggered they would shut
down their application until a manual VACUUM could be run.

--=20
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin