From: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: EXPLAIN omits schema? |
Date: | 2007-06-13 16:12:31 |
Message-ID: | dadb94ac7ba07d56b798458bd35e2774@biglumber.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
> And you stick them in a well-defined XML format (or another
> format if you happen to hate XML) where the client-side program can easily
> parse out whatever it needs. It's also future-proof - if you add a new
> field somewhere, the client program parser won't break.
>
> Something worth doing? Not to replace the current explain output, but as a
> second option (EXPLAIN XML whatever)?
This reminded me of a quick function I wrote up for my PGCon talk last month.
I've posted it on the blog:
I'd rather see tables with a convert-to-XML function than direct XML FWIW.
- --
Greg Sabino Mullane greg(at)turnstep(dot)com
End Point Corporation
PGP Key: 0x14964AC8 200706131211
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iD8DBQFGcBdnvJuQZxSWSsgRA/irAJsH0ZT3wLNN4mLirsTryiK1m9gyHwCg6+9A
0MuJqGxJ9gkEIWVUeq4iXag=
=NeB/
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Tolley | 2007-06-13 17:27:00 | \d omits schema on inherited tables (Was: EXPLAIN omits schema?) |
Previous Message | Gregory Stark | 2007-06-13 16:00:49 | Re: EXPLAIN omits schema? |