Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 7D1DE10D80A7 for ; Thu, 17 Nov 2011 20:34:04 -0400 (AST) Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RRCP5-0004KS-LZ for pgsql-performance@postgresql.org; Fri, 18 Nov 2011 00:34:04 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id pAI0XnXS014906; Thu, 17 Nov 2011 19:33:49 -0500 (EST) To: Jon Nelson cc: pgsql-performance@postgresql.org Subject: Re: external sort performance In-reply-to: References: Comments: In-reply-to Jon Nelson message dated "Thu, 17 Nov 2011 14:11:30 -0600" Date: Thu, 17 Nov 2011 19:33:49 -0500 Message-ID: <14905.1321576429@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 201111/226 X-Sequence-Number: 45737 Jon Nelson writes: > Is the sorting that is necessary for index creation unable to use a > hash table? (This is a standard btree index). Hash aggregation isn't sorting --- it's only useful for grouping. regards, tom lane