From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: One-Shot Plans |
Date: | 2011-06-14 18:38:14 |
Message-ID: | 201106141838.p5EIcEv16446@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Simon Riggs wrote:
> On Tue, Jun 14, 2011 at 7:28 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > Simon Riggs wrote:
> >> Currently, the planner and executor are mostly independent of each
> >> other: the planner doesn't really know when the plan will be executed,
> >> and the executor doesn't know how recently the plan was made.
> >>
> >> We can work out the various paths through the traffic cop to see when
> >> a plan will be a "one-shot" - planned and then executed immediately,
> >> then discarded.
> >
> > I was also hoping someday allow plans that are to be immediately
> > executed to probe the buffer cache to determine how expensive index
> > scans would be.
>
> Yes, it opens up many optimizations, both for cache sensitivity and
> dynamic data access.
>
> But those are later ideas based on the existence of this first step.
Agreed.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2011-06-14 18:39:15 | Re: ITYM DROP TABLE |
Previous Message | Radosław Smogura | 2011-06-14 18:37:04 | Crash dumps |