Re: View with an outer join - is there any way to optimise this? - Mailing list pgsql-general

From Tom Lane
Subject Re: View with an outer join - is there any way to optimise this?
Date
Msg-id 2312.1134427325@sss.pgh.pa.us
Whole thread Raw
In response to View with an outer join - is there any way to optimise this?  (Rich Doughty <rich@opusvl.com>)
Responses Re: View with an outer join - is there any way to optimise
List pgsql-general
Rich Doughty <rich@opusvl.com> writes:
> I have a view vw_tokens defined as
> ...
> I cannot however perform a meaningful join against this view.
> ...
> PG forms the full output of the view.

You seem to be wishing that PG would push the INNER JOIN down inside the
nested LEFT JOINs.  In general, rearranging inner and outer joins like
that can change the results.  There are limited cases where it can be
done without breaking the query semantics, but the planner doesn't
currently have any logic to analyze whether it's safe or not, so it just
doesn't try.

Improving this situation is (or ought to be) on the TODO list, but I dunno
when it will happen.

            regards, tom lane

pgsql-general by date:

Previous
From: Vivek Khera
Date:
Subject: Re: Performance large tables.
Next
From: Wes
Date:
Subject: Excessive vacuum times