Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 4BA9F6387B0 for ; Wed, 13 Jan 2010 13:02:47 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 95328-01 for ; Wed, 13 Jan 2010 17:02:36 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from gv-out-0910.google.com (gv-out-0910.google.com [216.239.58.184]) by mail.postgresql.org (Postfix) with ESMTP id 6E17963864C for ; Wed, 13 Jan 2010 13:02:36 -0400 (AST) Received: by gv-out-0910.google.com with SMTP id y18so206067gvf.7 for ; Wed, 13 Jan 2010 09:02:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=5S/AhxHk7Cskvh/5+XRmxd6gi4ppvDEqtrTUChAGzBg=; b=TDVYSUTyZwdpypnPCTEgNmmA6S8ORAMGSCW4R0JUCXn27QB4vt4ppoxNvHj7AiWa6K jIlK01PoRdJS0ZUn/RHYCzQFU3yDqoUAYcO8fglLIwOS4atKF7Og7n1WzN1zhHHFuLiB 98Md+0vGhcQJ465Dsfk++givxYaqz+CrPxS1g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=hi6tDSNcKDifp5P6pL0sBxQW4U50zwZELnCIwBCC91btbQddjsEFsUeiuTn0zwMJMZ I5X4oO3KYmaZTr3e3S1lsBx41tYctuDlsyU6KZFkxc3wlISEpeLKl/JZv9vLF1DfqoaI Wv2qod3WjsSdWZjLCAAfWMMRNCZ3444nmJYzQ= MIME-Version: 1.0 Received: by 10.239.159.203 with SMTP id z11mr906637hbc.183.1263402154635; Wed, 13 Jan 2010 09:02:34 -0800 (PST) In-Reply-To: <14395.1263401611@sss.pgh.pa.us> References: <3073cc9b0908191745o3dc63d95q6b9308ef5bd199f2@mail.gmail.com> <3073cc9b1001111116x53427c9bm1e448128a3b4f6c6@mail.gmail.com> <18803.1263241120@sss.pgh.pa.us> <3073cc9b1001122231m1a15d187lae2a8096a813361b@mail.gmail.com> <603c8f071001130723v634cb3c3u1604ea69efb04e91@mail.gmail.com> <10990.1263397358@sss.pgh.pa.us> <603c8f071001130811g22387928g72262638532370e5@mail.gmail.com> <3073cc9b1001130814t79b313dk4377996dee0ac521@mail.gmail.com> <603c8f071001130824u3e0be910lfea14c3e475c8256@mail.gmail.com> <14395.1263401611@sss.pgh.pa.us> Date: Wed, 13 Jan 2010 12:02:34 -0500 Message-ID: <603c8f071001130902h45f1a6b4yd99b6558ca9e85d1@mail.gmail.com> Subject: Re: [PERFORMANCE] work_mem vs temp files issue From: Robert Haas To: Tom Lane Cc: Jaime Casanova , decibel , psql performance list Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.589 tagged_above=-10 required=5 tests=BAYES_00=-2.599, FH_DATE_PAST_20XX=3.188 X-Spam-Level: X-Archive-Number: 201001/258 X-Sequence-Number: 37138 On Wed, Jan 13, 2010 at 11:53 AM, Tom Lane wrote: > Robert Haas writes: >> Yeah. =A0My question is whether it's acceptable to add an extra line to >> the EXPLAIN output for every hash join, even w/o ANALYZE. > > We could add it if either VERBOSE or ANALYZE appears. =A0Not sure if > that's just too much concern for backwards compatibility, though. I think having it controlled by either of two options is to weird. I'm not worried so much about backward compatibility as I am about cluttering the output. Maybe making it controlled by VERBOSE is the right thing to do, although I'm sort of tempted to figure out if there is more useful instrumentation that could be done and put it all under a new option called, say, HASH_DETAILS. Not sure what else we could show though. ...Robert