From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andreas Pflug <Andreas.Pflug@web.de>
Cc: pgsql-performance@postgresql.org
Subject: Re: inefficient query plan with left joined view
Date: Tue, 28 Jan 2003 13:30:07 -0500
Message-ID: <22633.1043778607@sss.pgh.pa.us> (raw)
In-Reply-To: <3E36B4F2.1020506@web.de>
References: <3E36B4F2.1020506@web.de>
Andreas Pflug <Andreas.Pflug@web.de> writes:
> What I'm doing on V7.3.1:
> select t1.keycol, t2.keycol
> from tab1 t1
> LEFT join myview t2 on t1.keycol=t2.keycol
> where t1.keycol=1000001
> the view is created as
> CREATE myview AS SELECT keycol, 22::integer as calc_col FROM tab2
The subquery isn't pulled up because it doesn't pass the
has_nullable_targetlist test in src/backend/optimizer/plan/planner.c.
If we did flatten it, then references to calc_col wouldn't correctly
go to NULL when the LEFT JOIN should make them do so --- they'd be
22 all the time.
As the notes in that routine say, it could be made smarter: strict
functions of nullable variables could be allowed. So if your real
concern is not '22' but something like 'othercol + 22' then this is
fixable.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, Andreas.Pflug@web.de
Subject: Re: inefficient query plan with left joined view
In-Reply-To: <22633.1043778607@sss.pgh.pa.us>
References: <3E36B4F2.1020506@web.de> <22633.1043778607@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox