Re: Do CustomScan as not projection capable node
| От | Robert Haas |
|---|---|
| Тема | Re: Do CustomScan as not projection capable node |
| Дата | |
| Msg-id | CA+Tgmobf7GocuuD_KLqKj-pMRGVSxLL8=vsVwXZg_fojG2gkrg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Do CustomScan as not projection capable node (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Do CustomScan as not projection capable node
|
| Список | 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 по дате отправления: