On Fri, Feb 26, 2010 at 7:03 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> Basically, what I really want here is some kind of keyword or other
>> syntax that I can stick into a PL/pgsql query that requests a replan
>> on every execution.
> Wouldn't it be better if it just did the right thing automatically?
> The sort of heuristic I'm envisioning would essentially do "replan every
> time" for some number of executions, and give up only if it noticed that
> it wasn't getting anything better than the generic plan. So you'd have
> a fixed maximum overhead per session when the custom plan was useless,
> and the Right Thing when it wasn't.
Which is likely useless for my use case.
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2010-02-28 01:02:28|
|Subject: Re: add_path optimization|
|Previous:||From: Robert Haas||Date: 2010-02-28 01:00:52|
|Subject: Re: Re: Hot Standby query cancellation and Streaming Replication integration|