Re: New CORRESPONDING clause design

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Surafel Temsgen <surafel3000(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: New CORRESPONDING clause design
Date: 2017-02-19 16:43:23
Message-ID: CA+TgmoYMgtcJnoVhE73vGkX_1Hyqj06FcXZ-xocdhth=LJn-Hg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 16, 2017 at 8:28 PM, Surafel Temsgen <surafel3000(at)gmail(dot)com> wrote:
> Here is the implementation of the clause with the slight change, instead of
> doing column mapping for each side of leaf Queries in planner I make the
> projection nodes output to corresponding column lists only.
>
> This patch compiles and tests successfully with master branch on
> ubuntu-15.10-desktop-amd64.It also includes documentation and new regression
> tests in union.sql.

You should probably add this to https://commitfest.postgresql.org/ so
that it doesn't get forgotten about.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-02-19 16:58:54 Re: case_preservation_and_insensitivity = on
Previous Message Robert Haas 2017-02-19 16:41:13 Re: Passing query string to workers