From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Peter Geoghegan <pg(at)bowt(dot)ie>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Pavan Deolasee <pavan(dot)deolasee(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] MERGE SQL Statement for PG11 |
Date: | 2018-03-27 11:30:54 |
Message-ID: | CANP8+jKd1uAa6VomTUDroiYdtAQWOzbx9ntA6GT3+8PbBeWCyQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 27 March 2018 at 11:46, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 27 March 2018 at 10:31, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> wrote:
>
>> Fixed in v26.
>
> More comments on v26
In terms of further performance optimization, if there is just one
WHEN AND condition and no unconditional WHEN clauses then we can add
the WHEN AND easily to the join query.
That seems like an easy thing to do for PG11
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2018-03-27 11:42:13 | Re: [HACKERS] why not parallel seq scan for slow functions |
Previous Message | Robert Haas | 2018-03-27 11:27:31 | Re: Parallel safety of binary_upgrade_create_empty_extension |