| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Vlad Arkhipov <arhipov(at)dc(dot)baikal(dot)ru> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: System catalog vacuum issues |
| Date: | 2013-08-06 07:00:46 |
| Message-ID: | 52009F1E.2070901@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08/06/2013 01:56 PM, Vlad Arkhipov wrote:
> Hello,
>
> We are suffering from a long-standing issue with autovacuuming/vacuuming
> system catalogs on the production server. We are actively using
> temporary tables in the legacy application, so system catalogs grows
> unbounded in time. Autovacuum does not remove dead tuples and neither do
> the manual vacuum. We are running PostgreSQL 9.2.4 on Linux 2.6.18 x86_64.
>
> Nobody's holding an open transaction for long periods.
Got any prepared transactions?
SELECT * FROM pg_prepared_xacts;
SHOW max_prepared_transactions;
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-08-06 07:06:59 | Re: mvcc catalo gsnapshots and TopTransactionContext |
| Previous Message | Amit Kapila | 2013-08-06 06:18:32 | Re: Move unused buffers to freelist |