Re: update tuple routing and triggers - Mailing list pgsql-hackers

From Amit Langote
Subject Re: update tuple routing and triggers
Date
Msg-id 1db54a66-cf39-3e94-7e71-ffd5a92546cc@lab.ntt.co.jp
Whole thread Raw
In response to update tuple routing and triggers  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: update tuple routing and triggers  (Amit Khandekar <amitdkhan.pg@gmail.com>)
Re: update tuple routing and triggers  (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>)
List pgsql-hackers
On 2018/02/06 10:48, Amit Langote wrote:
> When working on this, I wondered if the es_leaf_result_relations should
> actually be named something like es_tuple_routing_result_rels, to denote
> the fact that they're created by tuple routing code.  The current name
> might lead to someone thinking that it contains *all* leaf result rels,
> but that won't remain true after this patch.  Thoughts?

While I'm waiting to hear some opinion on the renaming, I updated the
patch to clarify this in the comment about es_leaf_result_relations.

Thanks,
Amit

Attachment

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Add more information_schema columns
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] [PATCH] Lockable views