| From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | "David Wilson" <david(dot)t(dot)wilson(at)gmail(dot)com> |
| Cc: | mljv(at)planwerk6(dot)de, pgsql-general(at)postgresql(dot)org, "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
| Subject: | Re: Problem after VACUUM ANALYZE |
| Date: | 2008-04-09 08:16:25 |
| Message-ID: | 2e78013d0804090116u7e4a1000tc180060a9f408a41@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Apr 9, 2008 at 1:41 PM, David Wilson <david(dot)t(dot)wilson(at)gmail(dot)com> wrote:
>
>
> I've run into a very similar problem. I have some long-running
> processes that generate a large amount of data and then query that
> data that must periodically drop their connections and rebuild to
> ensure that query plans get re-planned according to updated
> statistics. This is especially true when a new DB is first being
> brought up with an initial set of data (~1 week of compute time, ~30gb
> of data and ~120m rows) with processes that live through the entire
> process.
>
I believe plan-invalidation in 8.3 should address this. Isn't it ?
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mljv | 2008-04-09 08:17:39 | Re: Problem after VACUUM ANALYZE |
| Previous Message | David Wilson | 2008-04-09 08:11:29 | Re: Problem after VACUUM ANALYZE |