Re: Do CustomScan as not projection capable node - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Do CustomScan as not projection capable node
Date
Msg-id CA+Tgmobf7GocuuD_KLqKj-pMRGVSxLL8=vsVwXZg_fojG2gkrg@mail.gmail.com
Whole thread Raw
In response to Re: Do CustomScan as not projection capable node  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Do CustomScan as not projection capable node
List pgsql-hackers
On Fri, Apr 19, 2019 at 12:45 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I don't buy this for a minute.  Where do you think projection is
> going to happen?  There isn't any existing node type that *couldn't*
> support projection if we insisted that that be done across-the-board.
> I think it's mostly just a legacy thing that some don't.

I think there may actually be some good reasons for that.  If
something like an Append or Material node projects, it seems to me
that this means that we built the wrong tlist for its input(s).

That justification doesn't apply to custom scans, though.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: display of variables in EXPLAIN VERBOSE
Next
From: David Fetter
Date:
Subject: Re: [PATCH v1] Add \echo_stderr to psql