Re: Bug: 8.0 beta1 either view optimization or pgdump/pgrestore - Mailing list pgsql-general

From Sim Zacks
Subject Re: Bug: 8.0 beta1 either view optimization or pgdump/pgrestore
Date
Msg-id 385834187.20041028085420@compulab.co.il
Whole thread Raw
In response to Re: Bug: 8.0 beta1 either view optimization or pgdump/pgrestore  (Sim Zacks <sim@compulab.co.il>)
List pgsql-general
On second thought another way to optimize a query like that would be
to remove the * and only put in the columns that are actually being
used, as opposed to taking the * literally.
Such that if the fields in the select list use 2 columns and the join
uses 1 column, only those 3 columns should be expanded by the
optimizer. This would probably make the query more efficient as well,
being that it selects fewer fields.

Thank You
Sim Zacks
IT Manager
CompuLab
04-829-0145 - Office
04-832-5251 - Fax


pgsql-general by date:

Previous
From: Sim Zacks
Date:
Subject: Re: Bug: 8.0 beta1 either view optimization or pgdump/pgrestore
Next
From: Thomas Hallgren
Date:
Subject: Re: Reasoning behind process instead of thread based