-----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: http://people.planetpostgresql.org/greg/index.php?/archives/106-Putting-EXPLAIN-results-into-a-table.html I'd rather see tables with a convert-to-XML function than direct XML FWIW. - -- Greg Sabino Mullane [EMAIL PROTECTED] 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----- ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
