| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
| Subject: | Re: update tuple routing and triggers |
| Date: | 2018-02-06 02:38:09 |
| Message-ID: | 1db54a66-cf39-3e94-7e71-ffd5a92546cc@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 | Content-Type | Size |
|---|---|---|
| v2-0001-Fix-trigger-behavior-with-update-tuple-routing.patch | text/plain | 2.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-02-06 03:00:44 | Re: [HACKERS] [PATCH] Lockable views |
| Previous Message | Peter Eisentraut | 2018-02-06 01:59:31 | Add more information_schema columns |