From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
Cc: | Florian Weimer <fweimer(at)bfk(dot)de>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Invalid YAML output from EXPLAIN |
Date: | 2010-06-07 17:44:10 |
Message-ID: | 18708.1275932650@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Greg Smith <greg(at)2ndquadrant(dot)com> writes:
> The complaints about YAML taking up too much vertical space are
> understandable, but completely opposite of what I care about. I can
> e-mail a customer a YAML plan and it will survive to the other side and
> even in a reply back to me. Whereas any non-trivial text format one is
> guaranteed to utterly destroyed by line wrapping along the way.
> I think this thread could use a fresh example to remind anyone who
> hasn't played with the curent YAML format what it looks like.
So? This doesn't look amazingly unlike the current JSON output,
and to the extent that we have to add more quoting to it, it's
going to look even more like the JSON output.
Given the lack of any field separators other than newlines, I'm also
finding myself extremely doubtful about the claim that it survives
line-wrapping mutilations well. For instance this bit:
- Node Type: Seq Scan
Parent Relationship: Outer
doesn't appear to have anything but whitespace to distinguish it from
- Node Type: Seq Scan Parent
Relationship: Outer
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2010-06-07 18:26:24 | Re: [BUGS] Invalid YAML output from EXPLAIN |
Previous Message | Greg Smith | 2010-06-07 17:34:38 | Re: [HACKERS] Invalid YAML output from EXPLAIN |
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2010-06-07 17:56:26 | Re: nvarchar notation accepted? |
Previous Message | Greg Smith | 2010-06-07 17:34:38 | Re: [HACKERS] Invalid YAML output from EXPLAIN |