From: | Erik Jones <ejones(at)engineyard(dot)com> |
---|---|
To: | Bryce Nesbitt <bryce2(at)obviously(dot)com> |
Cc: | sql pgsql <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Way to eliminate pg_dump activity from pg_stat_all ? |
Date: | 2008-12-17 00:33:21 |
Message-ID: | 78FDD2B4-B430-4521-8656-47ECF9D67413@engineyard.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
I doubt it. From the server's perspective, pg_dump is just a client
executing queries. If the db is never used, why are you continually
backing it up?
On Dec 16, 2008, at 12:55 PM, Bryce Nesbitt wrote:
> I've got a bunch of tables in a legacy database that I know are
> never used, and some more I'm not sure about. So I tried to
> identify and confirm with:
> select pg_stat_reset();
>
> -- Wait a long time
>
> select * from pg_stat_all_tables where schemaname='public' order by
> seq_scan,seq_tup_read;
> select greatest(heap_blks_read,heap_blks_hit),relname from
> pg_statio_all_tables where schemaname='public' order by 1 desc;
> But I think I'm getting clutter from the nightly backups. Is there
> a way to keep pg_dump activity out of the statistics? I can think of
> several reasons to want such activity excluded, not just this one.
Erik Jones, Database Administrator
Engine Yard
Support, Scalability, Reliability
866.518.9273 x 260
Location: US/Pacific
IRC: mage2k
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-12-17 00:38:10 | Re: pg_clog/0202 Error |
Previous Message | Bryce Nesbitt | 2008-12-16 20:55:42 | Way to eliminate pg_dump activity from pg_stat_all ? |