Re: further explain changes
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Jaime Casanova <jcasanov@systemguards.com.ec>,
pgsql-hackers@postgresql.org
Date: 2010-01-24T17:30:26Z
Lists: pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes: > On Sun, Jan 24, 2010 at 12:06 AM, Jaime Casanova >> why not let it go in ANALYZE, just as the sort info > It's kinda long-winded - it adds like 4 extra lines for each hash > join. I don't think I want to add that much clutter to regular E-A > output. Well, that would only happen if you're deliberately obtuse about the formatting. The sort code manages to fit all the extra on one line, and I don't see why hash couldn't. I'd vote for just adding it in the exact same cases that sort adds extra info. -1 for either adding a new option or changing the meaning of the ones that are there. regards, tom lane