Re: Query plan question, and a memory leak - Mailing list pgsql-general

From Tom Lane
Subject Re: Query plan question, and a memory leak
Date
Msg-id 8415.1044255574@sss.pgh.pa.us
Whole thread Raw
In response to Re: Query plan question, and a memory leak  (Greg Stark <gsstark@mit.edu>)
Responses Re: Query plan question, and a memory leak  (Greg Stark <gsstark@mit.edu>)
Re: Query plan question, and a memory leak  (Greg Stark <gsstark@mit.edu>)
List pgsql-general
Greg Stark <gsstark@mit.edu> writes:
> Is there some way to force the optimizer not to substitute the subquery in the
> where clause?

You could try tinkering with the rules for invoking subquery_push_qual
in src/backend/optimizer/path/allpaths.c.  This might be a case that
would fall under the note there wondering if pushing down can ever
result in a worse plan.  I'm not sure though that we can tell the
difference reliably...

            regards, tom lane

pgsql-general by date:

Previous
From: Ryan VanderBijl
Date:
Subject: Re: serialization errors
Next
From: Christoph Dalitz
Date:
Subject: List online archives and spam