Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 549E72E002C for ; Sun, 22 Jun 2008 05:54:31 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 42897-04 for ; Sun, 22 Jun 2008 05:54:24 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smtp-out.freesurf.fr (fructidor.freesurf.fr [212.43.206.30]) by developer.postgresql.org (Postfix) with ESMTP id 45F412E0031 for ; Sun, 22 Jun 2008 05:54:26 -0300 (ADT) Received: by smtp-out.freesurf.fr (Postfix, from userid 1000) id 9DFC64C02F; Sun, 22 Jun 2008 11:20:57 +0200 (CEST) Received: from freesurf.fr (georges.freesurf.fr [212.43.206.67]) by smtp-out.freesurf.fr (Postfix) with ESMTP id 7025B4C02C for ; Sun, 22 Jun 2008 11:20:57 +0200 (CEST) Received: from 210.146.69-86.rev.gaoland.net (210.146.69-86.rev.gaoland.net [86.69.146.210]) by webmail-html.freesurf.fr (Horde Framework) with HTTP; Sun, 22 Jun 2008 10:54:20 +0200 Message-ID: <20080622105420.141763mydlqmofks@webmail-html.freesurf.fr> Date: Sun, 22 Jun 2008 10:54:20 +0200 From: hjeancha@freesurf.fr To: pgsql-admin@postgresql.org Subject: Re: vacuumdb not enough stack items References: <20080621154752.33867bg7xhmsv04c@webmail-html.freesurf.fr> <19830.1214066236@sss.pgh.pa.us> In-Reply-To: <19830.1214066236@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.2-RC2) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.364 tagged_above=0 required=5 tests=AWL=-0.455, MIME_QP_LONG_LINE=1.819 X-Spam-Level: * X-Archive-Number: 200806/193 X-Sequence-Number: 29531 Tom Lane a =E9crit=A0: > hjeancha@freesurf.fr writes: >> i use postgresql version7.4.7 on i386-pc-linux-gnu, autovacuum is >> configured to run on this database. > > Hmm ... in theory autovacuum should have kept you out of trouble, > if it was working properly. Were you keeping an eye on its log > output? > >> Doing a manual vacuumdb on each database raise an error message saying: >> vacuumdb: vacuuming of database "ez_info1" failed: ERREUR: not enough >> stack items > > What probably happened was that this error blocked autovacuum from > completing an anti-wraparound vacuum :-( > > [ checks code... ] This appears to indicate a corrupted btree index. > I don't believe we've ever heard of this error occurring in the field > before, so it might be interesting to inquire into exactly what happened > to the index --- but if you just want to get out of trouble I'd suggest > =09* VACUUM VERBOSE as superuser. > =09 Watch the output to determine which table it fails on. > =09* REINDEX that table. > =09* VACUUM VERBOSE again. > This should solve the problem fairly painlessly as long as the > corrupted index isn't on a system catalog. If it is, see the > man page for REINDEX about how to recover. > > I'm not sure if vacuuming will get your data back at this point, > but it's certainly worth a try. > > Somewhere in here you should think about moving to a more modern > Postgres release. 8.1 and later wouldn't have let you keep going > to the point of wraparound with a critical problem like this. > > =09=09=09regards, tom lane > > -- > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin > Not really, because i was not in charge of this database until now. I found that in file /etc/postgresql/postmaster.conf, autovacuum is set to N= O. and stats_start_collector =3D false , stats_row_level =3D false in =20 postgresql.conf file. I'm not really sure if autovacuum is really running. I found old log file from autovacuum on the server, but today's log =20 file is missing. I will give it a try and let you know, but for now, other databases =20 with age(datfrozenxid) with negative values seems to be ok. From what you are saying, i understand that it's urgent to 1) VACUUM VERBOSE and REINDEX 2) if it's not OK make an initdb and recreate databases if possible in =20 postgresql minimum release 8.1. I'll try to convince the application administrator that this a =20 priority to upgrade recent version of postgresql. Thanks a lot