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

From Robert Haas
Subject Re: Avoiding bad prepared-statement plans.
Date
Msg-id 603c8f071002260851k6ef85d23w1edbdd8e0eae1a3a@mail.gmail.com
Whole thread Raw
In response to Re: Avoiding bad prepared-statement plans.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Avoiding bad prepared-statement plans.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Feb 26, 2010 at 10:07 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I think this is basically a planner problem and should be fixed in the
> planner, not by expecting users to make significant changes in
> application logic in order to create an indirect effect.

I would agree if I thought that were possible, but I'm skeptical about
your proposed solution.

...Robert


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Avoiding bad prepared-statement plans.
Next
From: Robert Haas
Date:
Subject: Re: Avoiding bad prepared-statement plans.