| From: | Joshua Tolley <eggyknap(at)gmail(dot)com> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Subject: | Re: generic options for explain |
| Date: | 2009-05-26 16:34:07 |
| Message-ID: | 20090526163407.GL22115@eddie |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 26, 2009 at 09:55:55AM -0400, Dave Page wrote:
> from the pgAdmin perspective. We
> already use libxml2, but JSON would introduce another dependency for
> us.
...and using XML introduces a dependency for those that apps that don't already
use some XML parser. I realize that since the pool of apps that care to
mechanically parse EXPLAIN output is small, it wouldn't necessarily be a big
deal to hand each of them a new dependency in the form of a parser for XML,
JSON, etc. But we know the least common denominator is to return a set of
tuples; let's make sure that really is unworkable before forcing even that
dependency.
- Josh / eggyknap
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-05-26 16:36:30 | Re: PostgreSQL Developer meeting minutes up |
| Previous Message | Greg Stark | 2009-05-26 16:28:56 | Re: problem with memory |