Re: ON CONFLICT DO UPDATE for partitioned tables

From: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, Andres Freund <andres(at)anarazel(dot)de>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie>
Subject: Re: ON CONFLICT DO UPDATE for partitioned tables
Date: 2018-04-18 04:35:02
Message-ID: f6c11141-9569-7b0f-eb24-061baef44c9f@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2018/04/18 0:04, Alvaro Herrera wrote:
> Amit Langote wrote:
>
>> I just confirmed my hunch that this wouldn't somehow do the right thing
>> when the OID system column is involved. Like this case:
>
> This looks too big a patch to pursue now. I'm inclined to just remove
> the equalTupdesc changes.

OK. Here is the patch that removes equalTupdesc optimization.

I will add the rest of the patch to the next CF after starting a new
thread for it sometime later.

Thanks,
Amit

Attachment Content-Type Size
v1-0001-Remove-equalTupDescs-based-optimization-in-ExecIn.patch text/plain 7.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2018-04-18 05:04:17 Re: Excessive PostmasterIsAlive calls slow down WAL redo
Previous Message Amit Langote 2018-04-18 04:13:38 Re: ON CONFLICT DO UPDATE for partitioned tables