Re: Avoiding bad prepared-statement plans. - Mailing list pgsql-hackers

From Bart Samwel
Subject Re: Avoiding bad prepared-statement plans.
Date
Msg-id ded01eb21002110448h3a452e8fwefe575bd869ec04@mail.gmail.com
Whole thread Raw
In response to Re: Avoiding bad prepared-statement plans.  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Avoiding bad prepared-statement plans.
List pgsql-hackers
On Thu, Feb 11, 2010 at 13:41, Robert Haas <robertmhaas@gmail.com> wrote:
On Thu, Feb 11, 2010 at 7:39 AM, Bart Samwel <bart@samwel.tk> wrote:
> Anyhow, I have no clue how much time the planner takes. Can anybody provide
> any statistics in that regard?

It depends a great deal on the query, which is one of the things that
makes implementing this rather challenging.

But I guess you can probably expect it to be on the same order for the same query in generic form and with filled-in parameters? Because that's the underlying assumption of the "ratio" criterion -- that re-planning with filled-in parameters takes about as much time as the initial planning run took.

Cheers,
Bart

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while
Next
From: Robert Haas
Date:
Subject: Re: knngist patch support