Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 1929A2E008C for ; Tue, 10 Jun 2008 12:20:12 -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 56022-03 for ; Tue, 10 Jun 2008 12:19:35 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181]) by developer.postgresql.org (Postfix) with ESMTP id 1720F2E0073 for ; Tue, 10 Jun 2008 12:19:34 -0300 (ADT) Received: by py-out-1112.google.com with SMTP id d37so1115664pye.29 for ; Tue, 10 Jun 2008 08:19:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=sUaAgA6yrFrSY4K9dKuFBSH/Y58uI3grRwrDuGgL+Fo=; b=e/Jr8mW3BeE508VQnRclPq/f/pVqLlZ43OuTes6B1QcPgbk94pUvRNOPBySfxWojOo U9Mci5zxor/VZsR/BLAL+xq2CxWUfRzuu/QleRKlgsJtZMbZaKKEVS07LjnE0ayvVkUz Z96CuL78j8gzS+0fDPkVoClVYiMEfL5cfSEyk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=Y90/JwGgNNxcuUBKhI7uszTeHUCyAjQmnj2GEaqe8C8h0vBMx0GLAg56snryZCfomW ujS6qlpXT+E8D6kEz181jwMFZZ8FfywP7utPHkQWR/9UyDV+AeHc/0CuohWMq7I6Ab6O 6GusbKTUfTxEqkD32teJUWnWYDoO+FiJ49tNg= Received: by 10.114.181.6 with SMTP id d6mr5075205waf.50.1213111173087; Tue, 10 Jun 2008 08:19:33 -0700 (PDT) Received: by 10.114.67.10 with HTTP; Tue, 10 Jun 2008 08:19:32 -0700 (PDT) Message-ID: Date: Tue, 10 Jun 2008 10:19:32 -0500 From: "Jaime Casanova" To: alex Subject: Re: postgres 'forgets' table definitions Cc: pgsql-admin@postgresql.org In-Reply-To: <484E88AB.6020505@kerkhove.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <484E61A0.5030706@kerkhove.net> <484E88AB.6020505@kerkhove.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/73 X-Sequence-Number: 29411 On Tue, Jun 10, 2008 at 8:59 AM, alex wrote: > Problem solved! > > After a vacuum full verbose analyze of all the pg_* tables everything is = fine again. > > I switched to a scripted vacuum about 6 months ago because some (history)= tables take way too long to vacuum and have static data anyway. But as it t= urns out I skipped all the pg_ tables since then. So they were not vacuumed= for quite some time. > > Even without vacuuming, I don't think postgres should ever behave like th= is, but I'm glad my problem is solved now. > vacuum is a need not a choice, specially with such an old version... http://www.postgresql.org/docs/7.3/static/routine-vacuuming.html#VACUUM-FOR= -WRAPAROUND in 8.3, there are a couple of improvments in that area that makes wraparound less frecuent but it is still a problem... and now the autovacuum is integrated so things are a lot better --=20 regards, Jaime Casanova Soporte y capacitaci=F3n de PostgreSQL Guayaquil - Ecuador Cel. (593) 87171157