Re: MERGE SQL statement for PG12

From: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: MERGE SQL statement for PG12
Date: 2019-01-14 06:37:27
Message-ID: CABOikdPL3qBohM7deqC5M-F8BkVSkdnEDytSupi5JtxS-egHZw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Robert,

Thanks for the comments.

On Fri, Jan 11, 2019 at 2:45 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

>
> I feel like there has been some other thread where this was discussed,
> but I can't find it right now. I think that the "query construction"
> logic in transformMergeStmt is fundamentally the wrong way to do this.
> I think several others have said the same.

Can you please help me understand what's fundamentally wrong with the
approach and more importantly, can you please explain what would the the
architecturally sound way to do this? The same also applies to the executor
side where the current approach is deemed wrong, but very little is said on
what's the correct way.

> And I don't think this
> should be considered for commit until that is rewritten.
>

I understand. I'm not suggesting that the patch is in committable shape, if
it wasn't last April, because nothing has changed since then. The purpose
of keeping it up-to-date is to solicit feedback and directions and to show
that my interest in the patch is still intact.

Thanks,
Pavan

--
Pavan Deolasee http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2019-01-14 06:39:42 Re: Reducing header interdependencies around heapam.h et al.
Previous Message Andrew Gierth 2019-01-14 06:21:14 Re: SPI Interface to Call Procedure with Transaction Control Statements?