Re: [HACKERS] New CORRESPONDING clause design - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: [HACKERS] New CORRESPONDING clause design
Date
Msg-id CAFj8pRCspwFhF1JVD-GKJS0rsojBC1r6okFmDtfVKiSu2XwD0g@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] New CORRESPONDING clause design  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: [HACKERS] New CORRESPONDING clause design  (Surafel Temesgen <surafel3000@gmail.com>)
List pgsql-hackers
Hi

2017-03-10 13:49 GMT+01:00 Pavel Stehule <pavel.stehule@gmail.com>:
Hi

2017-03-10 12:55 GMT+01:00 Pavel Stehule <pavel.stehule@gmail.com>:


2017-03-10 10:13 GMT+01:00 Surafel Temesgen <surafel3000@gmail.com>:

Yes, you are correct it should to work on CORRESPONDING clause case. SQL 20nn standard draft only said each query to be of the same degree in a case of set operation without corresponding clause. The attached patch is corrected as such .I add those new test case to regression test too


Thank you - I will recheck it.

 Fast check - it looks well

I am sending minor update - cleaning formatting and white spaces, error messages + few more tests

It is working very well.

Maybe correspondingClause needs own node type with attached location. Then context can be much better positioned.

Regards

Pavel
 

Regards

Pavel

Attachment

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [HACKERS] Write Ahead Logging for Hash Indexes
Next
From: Mark Kirkwood
Date:
Subject: [HACKERS] Logical replication initial feedback