Re: Query running slow but was running fine before

From: Bill Moran <wmoran(at)collaborativefusion(dot)com>
To: Keaton Adams <kadams(at)mxlogic(dot)com>
Cc: Dennis Brakhane <brakhane+psql(at)googlemail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Query running slow but was running fine before
Date: 2008-07-08 12:37:54
Message-ID: 20080708083754.290ded92.wmoran@collaborativefusion.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

In response to Keaton Adams <kadams(at)mxlogic(dot)com>:

> Good point. But....
>
> This is a database used to capture logged information, such as
> success/failure of an operation. Daily tables are rolled up to weekly
> tables, weekly tables are rolled up to monthly tables. All logged
> activity are done by inserts, never any updates or deletes, to avoid
> having to do a vacuum full. So rows are added for seven days to the
> weekly table (kda_log_info_2008w24) and that's it. Once a new week
> begins the data is static until enough weeks pass by where the weekly
> information is summarized at a higher level and stored in a monthly
> table, then the weekly table is dropped.
>
> I'll send out a full EXPLAIN from the original query, which was against
> the view, so you can see the scope of the issue.

Please also send the output of:
SELECT relname, n_tup_ins, n_tup_upd, n_tup_del, n_live_tup, n_dead_tup FROM pg_stat_user_tables ;

--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/

wmoran(at)collaborativefusion(dot)com
Phone: 412-422-3463x4023

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Leif B. Kristensen 2008-07-08 13:12:44 Re: select command doesnot work
Previous Message Raymond O'Donnell 2008-07-08 12:33:29 Re: select command doesnot work