Re: Display of multi-target-table Modify plan nodes in EXPLAIN

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Display of multi-target-table Modify plan nodes in EXPLAIN
Date: 2015-03-23 05:21:44
Message-ID: 13898.1427088104@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> writes:
> On Sun, Mar 22, 2015 at 6:32 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> What I'm imagining instead is that when there's more than one
>> target relation, we produce output like ...

> This looks better.
> In the format above, you have specified both the Remote SQL for scan as
> well as update but in the example you have only mentioned only Remote SQL
> for update; it may be part of "... etc ...". It's better to provide both.

Hm? We don't have scan nodes that read more than one table, so I'm
not following your point.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2015-03-23 05:23:23 Re: Order of enforcement of CHECK constraints?
Previous Message Ashutosh Bapat 2015-03-23 05:11:05 Re: Display of multi-target-table Modify plan nodes in EXPLAIN