From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
---|---|
To: | "Kuba Ouhrabka" <kuba(at)comgate(dot)cz> |
Cc: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: cached plans in plpgsql |
Date: | 2005-10-20 15:03:58 |
Message-ID: | 6EE64EF3AB31D5448D0007DD34EEB3417DD640@Herge.rcsinc.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Kuba wrote:
> is there an easy way to flush all cached query plans in pl/pgsql
> functions? I've long running sessions where data are changing and the
> plans become inaccurate after a while. I can imagine something like
> recreating all pl/pgsql functions. I can recreate them from sql source
> files but I'd prefer recreating them inside the database without
> accessing files outside. I can think only of one way - reconstructing
> function source code from pg_proc and EXECUTEing it. But it's not the
> cleanest solution (there isn't saved the actual source code anywhere
so
> there could be problems with quoting etc.). Can you see any other
> possibility? How do you solve this problem? [And yes, I don't want to
> re-connect...]
Start here:
http://archives.postgresql.org/pgsql-hackers/2005-09/msg00690.php
Merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Kuba Ouhrabka | 2005-10-20 16:25:12 | Re: cached plans in plpgsql |
Previous Message | Tom Lane | 2005-10-20 14:15:19 | Re: [HACKERS] tuning seqscan costs |