From: | tomas(at)tuxteam(dot)de |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: generic options for explain |
Date: | 2009-05-25 11:05:07 |
Message-ID: | 20090525110507.GA29837@tomas |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[Sent by mistake to Robert Haas only at first try. No cure for fat
fingers, I guess]
On Sun, May 24, 2009 at 04:05:18PM -0400, Robert Haas wrote:
[...]
> I think XML output format is a complete distraction from the real
> issue here, which is that there are certain pieces of information that
> are sometimes useful but are not useful enough to justify including
> them in the EXPLAIN output 100% of the time. By just punting all that
> stuff to EXPLAIN XML, we're just saying that we're not interested in
> creating a workable set of options to allow users to pick and choose
> the information they care about - so instead we're going to dump a
> huge chunk of unreadable XML and then make it the user's problem to
> find a tool that will extract the details that they care about. Boo,
> hiss.
+1
In my experience, this happens with "XML the data description language"
many times, but I haven' seen the problem as well-stated as in your
mail.
Hard for humans to read, hard for machines to read, and often trying to
solve a problem it can't (in this case, selecting the needed information
_beforehand_).
Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFKGntjBcgs9XrR2kYRAk1/AJ4rnZFnU4PFM8AJkaYYYLRInYHJDQCbBbt2
lTwxydBBnXP1MgDxz+vcpM8=
=o2qW
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-05-25 11:14:56 | Re: generic options for explain |
Previous Message | Dimitri Fontaine | 2009-05-25 10:24:59 | Re: generic options for explain |