Re: Poor plan choice in prepared statement - Mailing list pgsql-performance

From david@lang.hm
Subject Re: Poor plan choice in prepared statement
Date
Msg-id alpine.DEB.1.10.0901011239140.15026@asgard.lang.hm
Whole thread Raw
In response to Re: Poor plan choice in prepared statement  ("Guillaume Smet" <guillaume.smet@gmail.com>)
Responses Re: Poor plan choice in prepared statement  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
On Thu, 1 Jan 2009, Guillaume Smet wrote:

> On Thu, Jan 1, 2009 at 9:24 PM,  <david@lang.hm> wrote:
>> forgive my ignorance here, but if it's unnamed how can you reference it
>> later to take advantage of the parsing?
>
> You can't. That's what unnamed prepared statements are for.
>
> It's not obvious to me that the parsing phase is worth any "caching".
> From my experience, the planning phase takes far much time on complex
> queries.

the poster who started this thread had a query where the parsing phase
took significantly longer than the planning stage.

David Lang

pgsql-performance by date:

Previous
From: "Guillaume Smet"
Date:
Subject: Re: Poor plan choice in prepared statement
Next
From: Tom Lane
Date:
Subject: Re: Poor plan choice in prepared statement