Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Way to eliminate pg_dump activity from pg_stat_all ?
- From: Bryce Nesbitt <bryce2(at)obviously(dot)com>
- To: sql pgsql <pgsql-sql(at)postgresql(dot)org>
- Subject: Way to eliminate pg_dump activity from pg_stat_all ?
- Date: Tue, 16 Dec 2008 12:55:42 -0800
- Message-id: <494815CE.5090907@obviously.com> <text/plain>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000000"> I've got a bunch of tables in a legacy database that I <i>know</i> are <i>never</i> used, and some more I'm not sure about. So I tried to identify and confirm with:<br> <blockquote><tt>select pg_stat_reset(); <br> <br> -- Wait a long time<br> <br> select * from pg_stat_all_tables where schemaname='public' order by seq_scan,seq_tup_read;<br> select greatest(heap_blks_read,heap_blks_hit),relname from pg_statio_all_tables where schemaname='public' order by 1 desc; </tt><br> </blockquote> 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.<br> </body> </html>
- Follow-Ups:
- Re: Way to eliminate pg_dump activity from pg_stat_all ?
- From: Erik Jones
- Re: Way to eliminate pg_dump activity from pg_stat_all ?
- Prev by Date: pg_clog/0202 Error
- Next by Date: Re: Way to eliminate pg_dump activity from pg_stat_all ?
- Previous by thread: pg_clog/0202 Error
- Next by thread: Re: Way to eliminate pg_dump activity from pg_stat_all ?
- Indexes: