| From: | Alexander Kuzmenkov <a(dot)kuzmenkov(at)postgrespro(dot)ru> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Jeff Davis <pgsql(at)j-davis(dot)com> |
| Subject: | Re: PoC: full merge join on comparison clause |
| Date: | 2017-10-04 13:08:41 |
| Message-ID: | 0e0a0cb9-f51e-f8a6-3829-50c3e38e33f9@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
As discussed earlier, I changed the way we work with mergeopfamilies. I
use the "is_equality" flag to indicate whether the clause is an equality
one, and fill mergeopfamilies for both equality and inequality operators.
The updated patch is attached (rebased to 20b6552242).
--
Alexander Kuzmenkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| Attachment | Content-Type | Size |
|---|---|---|
| full-merge-join-v4.patch | text/x-patch | 43.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeus Kronion | 2017-10-04 13:09:44 | Re: Possible SSL improvements for a newcomer to tackle |
| Previous Message | Ashutosh Bapat | 2017-10-04 12:28:16 | Re: Another oddity in handling of WCO constraints in postgres_fdw |