| From: | Ben Chobot <bench(at)silentmedia(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: how to invalidate a stored procedure's plan? |
| Date: | 2010-04-24 01:06:39 |
| Message-ID: | BEC3FF55-774C-4217-8987-AAD935B570E2@silentmedia.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Apr 23, 2010, at 6:00 PM, Tom Lane wrote:
> Ben Chobot <bench(at)silentmedia(dot)com> writes:
>> I have a procedure that queries a table. This should be fast because of an index, but some index bloat has caused the index to become expensive, and so the procedure has cached a plan that uses a full table scan. I've since fixed the index bloat, but the procedure still seems to be doing full table scans. Is there a non-disruptive way to invalidate the cached plan for that procedure globally?
>
> What PG version? In 8.3 and up an ANALYZE on any of the tables
> mentioned in the problem query should suffice.
>
> regards, tom lane
Heh, woops, sorry, it's 8.4, and yes, a simple table analyze was all I needed. Thanks!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | சிவகுமார் மா | 2010-04-24 01:54:58 | Re: Need help to identify stray row in a table |
| Previous Message | Tom Lane | 2010-04-24 01:00:01 | Re: how to invalidate a stored procedure's plan? |