From: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Invalid YAML output from EXPLAIN |
Date: | 2010-06-07 14:37:26 |
Message-ID: | 9beba770f7ea99c46219ac7f8dd80525@biglumber.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Tom Lane wrote:
...
> Egad ... this is supposed to be an easily machine-generatable format?
>
> If it's really as broken as the above suggests, I think we should
> rip it out while we still can.
Heh ... not like you to shrink from a challenge. ;)
I don't think the above would be particularly hard to implement myself,
but if it becomes a really big deal, we can certainly punt by simply
quoting anything containing an indicator (the special characters above).
It will still be 100% valid YAML, just with some excess quoting for the
very rare case when a value contains one of the special characters.
- --
Greg Sabino Mullane greg(at)turnstep(dot)com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201006071035
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAkwNA+4ACgkQvJuQZxSWSshSswCg81kd3FdYnQup1eLWGesm+vm+
VO8AoL1Fwil/vXfRdRHx4A4zZUTDbZuT
=oPDv
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-06-07 14:49:29 | Re: Invalid YAML output from EXPLAIN |
Previous Message | Andy Balholm | 2010-06-07 14:30:54 | Re: BUG #5490: INSERT doesn't force cast from text to timestamp |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-06-07 14:49:29 | Re: Invalid YAML output from EXPLAIN |
Previous Message | Magnus Hagander | 2010-06-07 14:35:48 | Re: Re: Mailing list archives (was Re: [HACKERS] mailing list archiver chewing patches) |