Re: generic options for explain - Mailing list pgsql-hackers

From Dave Page
Subject Re: generic options for explain
Date
Msg-id 937d27e10905260655j3dec3197k5c3bccf65b74e42a@mail.gmail.com
Whole thread Raw
In response to Re: generic options for explain  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: generic options for explain  (Magnus Hagander <magnus@hagander.net>)
Re: generic options for explain  (Peter Eisentraut <peter_e@gmx.net>)
Re: generic options for explain  (Joshua Tolley <eggyknap@gmail.com>)
List pgsql-hackers
On Tue, May 26, 2009 at 9:52 AM, Andrew Dunstan <andrew@dunslane.net> wrote:
>
> In libxml-enabled builds at least, this could presumably be done fairly
> easily via the XML functions, especially if we get XSLT processing into the
> core XML functionality as I hope we can do this release. In fact, the
> ability to leverage existing XML functionality to munge the output is the
> thing that swings me in favor of XML as the machine readable output format
> instead of JSON, since we don't have and aren't terribly likely to get an
> inbuilt JSON parser. It means we wouldn't need some external tool at all.

I was thinking something similar, but from the pgAdmin perspective. We
already use libxml2, but JSON would introduce another dependency for
us.

-- 
Dave Page
EnterpriseDB UK:   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: generic options for explain
Next
From: Alvaro Herrera
Date:
Subject: Re: problem with plural-forms