Re: [SQL] Way to eliminate pg_dump activity from pg_stat_all ?

2009-01-20 Thread Bryce Nesbitt
It is not the db that's never used. Various tables in the db are never used. This is a database that's been continually added to and modified for ten years -- sometimes cruft accumulates. It would be nice to get pg_dump activity out of the stats for another reason --- pg_dump adds to the sequ

Re: [SQL] Way to eliminate pg_dump activity from pg_stat_all ?

2009-01-20 Thread Erik Jones
On Jan 20, 2009, at 11:27 AM, Bryce Nesbitt wrote: It is not the db that's never used. Various tables in the db are never used. This is a database that's been continually added to and modified for ten years -- sometimes cruft accumulates. Understood. It would be nice to get pg_dump activ

Re: [SQL] Way to eliminate pg_dump activity from pg_stat_all ?

2009-01-20 Thread Bryce Nesbitt
Erik Jones wrote: It would be nice to get pg_dump activity out of the stats for another reason --- pg_dump adds to the sequential scan activity, in a way that does not represent the "typical" use of the database. Essentially pg_dump is an atypical user of the database, so it's stats are "dif