Received: from mta2.snet.net (mta2.snet.net [204.60.203.71]) by postgresql.org (Postfix) with ESMTP id 018DF4774A4 for ; Wed, 27 Feb 2002 13:20:16 -0500 (EST) Received: from pop.snet.net ([204.60.203.73]) by mta2.snet.net (8.12.1/8.12.1/SNET-smtp-1.1/D-1.1/O-1.1) with ESMTP id g1RIKDjt003756 for ; Wed, 27 Feb 2002 13:20:14 -0500 (EST) Received: from kencast.com (167.95.252.64.snet.net [64.252.95.167]) by pop.snet.net (8.12.1/8.12.1/SNET-pop-1.2/D-1.2/O-1.3) with ESMTP id g1RIK4a0011898 for ; Wed, 27 Feb 2002 13:20:11 -0500 (EST) Message-ID: <3C7D252A.3030608@kencast.com> Date: Wed, 27 Feb 2002 13:27:54 -0500 From: Wei Weng Reply-To: wweng@kencast.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020205 X-Accept-Language: en-us MIME-Version: 1.0 To: pgsql-sql@postgresql.org Subject: How slow is DISTINCT? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200202/438 X-Sequence-Number: 6859 I tend to use DISTINCT a lot in my queries to limit the repeated rows. Is that a good habbit? How exactly slow is DISTINCT being processed in SQL engines? (not limited to postgresql, though comments on postgresql would be most relevant) Thanks -- Wei Weng Network Software Engineer KenCast Inc.