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

From Guillaume Smet
Subject Re: Poor plan choice in prepared statement
Date
Msg-id 1d4e0c10901011129w443a096apac00c9d106669604@mail.gmail.com
Whole thread Raw
In response to Re: Poor plan choice in prepared statement  (david@lang.hm)
Responses Re: Poor plan choice in prepared statement
List pgsql-performance
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.

--
Guillaume

pgsql-performance by date:

Previous
From: david@lang.hm
Date:
Subject: Re: Poor plan choice in prepared statement
Next
From: david@lang.hm
Date:
Subject: Re: Poor plan choice in prepared statement