| From: | Michael Glaesemann <grzm(at)myrealbox(dot)com> |
|---|---|
| To: | Rick Gigger <rick(at)alpinenetworking(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: stored procedure performance |
| Date: | 2005-12-14 03:30:59 |
| Message-ID: | 92CFEAC3-0F93-4A73-B372-49E1EE3B54A8@myrealbox.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Dec 14, 2005, at 11:38 , Rick Gigger wrote:
> What actually fixes it is to run it a while and made sure there is
> a bunch of data there (even if it is deleted and not visible to
> anything) and run vacuum analyze. Then recreate the stored
> procedure. Then run the stored procedure.
What happens if you just run vacuum analyze before running the stored
procedure (i.e., skipping the recreate the stored procedure step)?
Running vacuum analyze (or at least just analyze) helps keep the
statistics used by the query planner up to date. Recreating the
function might just be a red herring.
Michael Glaesemann
grzm myrealbox com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-12-14 03:35:37 | Re: "incomplete startup packet" on SGI |
| Previous Message | Rick Gigger | 2005-12-14 02:38:56 | stored procedure performance |