From: | Vlad Arkhipov <arhipov(at)dc(dot)baikal(dot)ru> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: System catalog vacuum issues |
Date: | 2013-08-06 07:19:59 |
Message-ID: | 5200A39F.2050607@dc.baikal.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 08/06/2013 04:00 PM, Craig Ringer wrote:
> 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;
dcdb=# select * from pg_prepared_xacts;
transaction | gid | prepared | owner | database
-------------+-----+----------+-------+----------
(0 rows)
dcdb=# show max_prepared_transactions;
max_prepared_transactions
---------------------------
100
(1 row)
From | Date | Subject | |
---|---|---|---|
Next Message | Sergey Konoplev | 2013-08-06 07:26:55 | Re: System catalog vacuum issues |
Previous Message | Andres Freund | 2013-08-06 07:06:59 | Re: mvcc catalo gsnapshots and TopTransactionContext |