From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Cache plan invalidation |
Date: | 2007-05-05 14:48:09 |
Message-ID: | 200705051448.l45Em9a22750@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
> The current TODO list has:
>
> Dependency Checking
> ===================
>
> * Flush cached query plans when the dependent objects change,
> when the cardinality of parameters changes dramatically, or
> when new ANALYZE statistics are available
>
> A more complex solution would be to save multiple plans for different
> cardinality and use the appropriate plan based on the EXECUTE values.
>
> * Track dependencies in function bodies and recompile/invalidate
>
> This is particularly important for references to temporary tables
> in PL/PgSQL because PL/PgSQL caches query plans. The only workaround
> in PL/PgSQL is to use EXECUTE. One complexity is that a function
> might itself drop and recreate dependent tables, causing it to
> invalidate its own query plan.
>
> Which of these are done or not done?
Also, is this done:
* Invalidate prepared queries, like INSERT, when the table definition
is altered
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Kaltenbrunner | 2007-05-05 14:53:25 | Patch Status in the wiki |
Previous Message | Tom Lane | 2007-05-05 14:43:19 | Re: storage of sensor data with Fourier transforms |