Re: Removing width from EXPLAIN - Mailing list pgsql-hackers

From greg@turnstep.com
Subject Re: Removing width from EXPLAIN
Date
Msg-id f4d16ea6ce779b953ca25f080d903fa6@biglumber.com
Whole thread Raw
In response to Re: Removing width from EXPLAIN  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Removing width from EXPLAIN  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


I guess I was thinking about this:

http://groups.google.com/groups?selm=10897.953919427%40sss.pgh.pa.us

"Average width is pretty bogus because the thing really doesn't haveany idea of the average length of variable-length
columns. I'm thinkingabout improving that in the future, but it may not be worth the trouble,because the width isn't
usedfor very much."
 

I also think that it is used that much: if you look at all the EXPLAINS 
that have come across the various lists over the years, very few (if any) 
utilize the "width" in any important way. It's important for computing 
the cost, but I would like to suggest that the extra "noise" should be 
off by default as most people never make use of it, and an EXPLAIN ANALYZE 
is already quite verbose.

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200305201143

-----BEGIN PGP SIGNATURE-----
Comment: http://www.turnstep.com/pgp.html

iD8DBQE+ynErvJuQZxSWSsgRAsiKAKDXEaCPnhq8koIhnFNNPfm5HzhA9gCgszok
bBRBoL4Uoe8gqXzizeLlU2o=
=I1sV
-----END PGP SIGNATURE-----




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Suggestion GRANT ALTER, TRIGGER ON ALTER
Next
From: Josh Berkus
Date:
Subject: Re: Suggestion GRANT ALTER, TRIGGER ON ALTER