From: Jaime Casanova <systemguards@gmail.com>
To: alex <alex.pgsql@kerkhove.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: postgres 'forgets' table definitions
Date: Tue, 10 Jun 2008 10:19:32 -0500
Message-ID: <c2d9e70e0806100819u4469f62bm6986b337a9a32195@mail.gmail.com> (raw)
In-Reply-To: <484E88AB.6020505@kerkhove.net>
References: <484E61A0.5030706@kerkhove.net>
<484E88AB.6020505@kerkhove.net>
On Tue, Jun 10, 2008 at 8:59 AM, alex <alex.pgsql@kerkhove.net> 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 turns 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 this, 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
--
regards,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Guayaquil - Ecuador
Cel. (593) 87171157
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: systemguards@gmail.com, alex.pgsql@kerkhove.net
Subject: Re: postgres 'forgets' table definitions
In-Reply-To: <c2d9e70e0806100819u4469f62bm6986b337a9a32195@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox