Re: Optimizer issue -- bad query plan? - Mailing list pgsql-general

From Moshe Jacobson
Subject Re: Optimizer issue -- bad query plan?
Date
Msg-id CAJ4CxLm94R65bRbmq4x+XvGf3PUCPTvd6dGYu+aLtBSZzMWgog@mail.gmail.com
Whole thread Raw
In response to Re: Optimizer issue -- bad query plan?  (John R Pierce <pierce@hogranch.com>)
List pgsql-general

On Thu, Jun 5, 2014 at 6:09 PM, John R Pierce <pierce@hogranch.com> wrote:
why would you join 28 tables you're not using ??

The query is derived from a view. I want to select only one column from a view with many columns. I figured the optimizer would be smart enough in this case not to join all of the tables needed for the columns I wasn't referencing at all. 

I thought it might be that postgres couldn't optimize the query due to the fact that it was a view, so that's why I pulled out this portion to see if it would speed up. But it didn't.


Moshe Jacobson
Manager of Systems Engineering, Nead Werx Inc.
2323 Cumberland Parkway · Suite 201 · Atlanta, GA 30339

"Quality is not an act, it is a habit." -- Aristotle

pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: Optimizer issue -- bad query plan?
Next
From: David G Johnston
Date:
Subject: Re: Optimizer issue -- bad query plan?