| From: | "Gourish Singbal" <gourish(at)gmail(dot)com> |
|---|---|
| To: | "Chris Hoover" <revoohc(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: More Autovacuum Questions |
| Date: | 2006-05-16 18:09:23 |
| Message-ID: | 674d1f8a0605161109v1292daf1j509baf29442faadc@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
U can install pgstattuple module which is available in the contrib directory
and run it on production as
psql> \x
psql> select * from pgstattuple('public'.'tablename');
it displays the table_len, tuple_count, tuple_len, tuple_percent,
dead_tuple_count, dead_tuple_len,dead_tuple_percent,free_space,free_percent
for the table .
On 5/16/06, Chris Hoover <revoohc(at)gmail(dot)com> wrote:
>
> Thanks to those who answered my first question. I am looking at
> implementing autovacuuming on our new production 8.1.3 systems. I am
> reading the documentation on the various configuration parameters. The
> autovacuum_analyze_threshold and autovacuum_vacuum_threshold talk about the
> number of updated and deleted tuples. Is there anyway to calculate these
> numbers in a running database?
>
> The reason I'm asking is that we are having some sporadic slowness issues
> with our databases, and I'm wanting to see how the database looks during
> these times. I know that vacuuming some specific tables tends to fix the
> problem. So, if I can see what autovacuum might see, I could set the
> parameters correctly to try and fix the issue.
>
> Anyway, are these number available to me?
>
> Thanks,
>
>
> Chris
>
--
Best,
Gourish Singbal
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Frost | 2006-05-16 18:22:27 | Re: does wal archiving block the current client connection? |
| Previous Message | Chris Hoover | 2006-05-16 18:00:21 | More Autovacuum Questions |