From: | Sergey Konoplev <gray(dot)ru(at)gmail(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:44:16 |
Message-ID: | CAL_0b1tbdMO38TRX3CyFQc3HLTK7Y79JLS2qsH+0ekRm7-rVMw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Aug 6, 2013 at 12:37 AM, Vlad Arkhipov <arhipov(at)dc(dot)baikal(dot)ru> wrote:
>> What pgstattuple shows on this table?
>> http://www.postgresql.org/docs/9.2/interactive/pgstattuple.html
>>
>
> dcdb=# select * from pgstattuple('pg_catalog.pg_attribute');
> table_len | tuple_count | tuple_len | tuple_percent | dead_tuple_count |
> dead_tuple_len | dead_tuple_percent | free_space | free_percent
> ------------+-------------+-----------+---------------+------------------+----------------+--------------------+------------+--------------
> 6363938816 | 48786 | 6830040 | 0.11 | 1459439 |
> 204321460 | 3.21 | 5939017376 | 93.32
> (1 row)
I guess you need to VACUUM FULL pg_attribute, if it is possible in
your situation of course. If it is not, let me know, I have another
one tricky way of solving this problem in my mind.
--
Kind regards,
Sergey Konoplev
PostgreSQL Consultant and DBA
Profile: http://www.linkedin.com/in/grayhemp
Phone: USA +1 (415) 867-9984, Russia +7 (901) 903-0499, +7 (988) 888-1979
Skype: gray-hemp
Jabber: gray(dot)ru(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien | 2013-08-06 08:47:14 | pgbench progress report improvements |
Previous Message | Vlad Arkhipov | 2013-08-06 07:37:57 | Re: System catalog vacuum issues |