| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: machine-readable explain output |
| Date: | 2009-06-16 13:45:53 |
| Message-ID: | 4A37A211.4090409@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas wrote:
> 3. We have existing precedent for this design pattern in, e.g. table_to_xml
>
> http://www.postgresql.org/docs/current/interactive/functions-xml.html
>
>
Tables are flat, explain output is not.
If there is a relationship between the items then that needs to be
expressed in the XML structure, either by use of child nodes or
attributes. Relying on the sequence of nodes, if that's what you're
doing, is not a good idea, and will make postprocessing the XML using
XSLT, for example, quite a bit harder. (Processing a foo that comes
after a bar is possible but not as natural as processing a foo that is a
child or attribute of a bar)
Anyway, I think what this discussion points out is that we actually need
a formal XML Schema for this output.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-06-16 14:23:56 | Re: [PATCH] backend: compare word-at-a-time in bcTruelen |
| Previous Message | Andres Freund | 2009-06-16 13:30:58 | Re: machine-readable explain output |