| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | hlinnaka <hlinnaka(at)iki(dot)fi> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Display of multi-target-table Modify plan nodes in EXPLAIN |
| Date: | 2015-03-23 06:51:30 |
| Message-ID: | CAM3SWZS=2Baid-T9doZNNnM6UKeTN+fcM3HbHkQr_qa1X=hCnQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Mar 22, 2015 at 11:38 PM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> If we have promised that, I think we should break the promise. No
> application should depend on the details of EXPLAIN output, even if it's in
> JSON/YAML/XML format. EXPLAIN is used by humans, and by tools like pgAdmin
> that display the output for humans, so let's do what makes most sense for
> humans. Admin tools will have to deal with new node types, and also new plan
> structures in every new release anyway. And if an admin tool doesn't
> recognize the new format, it surely falls back to displaying them in some a
> reasonable generic form.
+1
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rajeev rastogi | 2015-03-23 10:01:40 | Materialiation is slower than non-materialized |
| Previous Message | Noah Misch | 2015-03-23 06:49:15 | Re: Zero-padding and zero-masking fixes for to_char(float) |