From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | "Little, Douglas" <douglas(dot)little(at)orbitz(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Forced quiesce |
Date: | 2010-11-08 15:05:24 |
Message-ID: | 1289228619-sup-7871@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Excerpts from Little, Douglas's message of jue oct 28 09:39:19 -0300 2010:
> Hi,
> We're having to vacuum full the system tables everyday due to the number of temp table drop/creates.
Seems to me that you're solving the wrong problem. I think you should
be doing very frequent lazy vacuum (not full) of certain system catalogs
to prevent bloat. That way you don't need the maintenance to be done
with exclusive locks.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-11-08 15:15:02 | Re: autovacuum launcher process eating up 17G+ of ram? |
Previous Message | Alvaro Herrera | 2010-11-08 15:01:51 | Re: autovacuum launcher process eating up 17G+ of ram? |