| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Invalid YAML output from EXPLAIN |
| Date: | 2010-06-09 19:50:47 |
| Message-ID: | 167.1276113047@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> writes:
> Hmm. Well it's quite subjective, but IMO it's already more readable
> than JSON regardless of whether or not values are quoted, simply
> because it doesn't have [ ] and { } for lists and maps, which for JSON
> adds significantly to the number of lines in longer plans.
Yeah. Also, I think it would be fair to not quote values that are known
constants (for example, Node Type: Seq Scan) and are chosen to not need
quoting. It's just the things that are variables that worry me.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-06-09 19:56:58 | Re: Invalid YAML output from EXPLAIN |
| Previous Message | Dean Rasheed | 2010-06-09 19:38:10 | Re: Invalid YAML output from EXPLAIN |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-06-09 19:56:58 | Re: Invalid YAML output from EXPLAIN |
| Previous Message | Robert Haas | 2010-06-09 19:47:55 | Re: No hash join across partitioned tables? |