Re: update tuple routing and triggers

From: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
To: Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
Subject: Re: update tuple routing and triggers
Date: 2018-02-06 05:54:12
Message-ID: a5852710-e1ba-1fcb-9589-648d5625cc4d@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2018/02/06 13:56, Amit Khandekar wrote:
> I was wondering whether the same duplicate result rels issue can arise
> for es_root_result_relations and es_result_relations. But I think for
> inserts, es_root_result_relations is NULL, and for updates, these two
> lists always have distinct set of relations. So this issue might not
> be there for these two lists.

Yeah, we don't need to worry about es_root_result_relations.

Thanks,
Amit

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavan Deolasee 2018-02-06 06:06:36 Re: [HACKERS] MERGE SQL Statement for PG11
Previous Message Amit Langote 2018-02-06 05:52:18 Re: update tuple routing and triggers