X-Original-To: pgsql-students-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id A11AA9FA5B5 for ; Mon, 5 Jun 2006 16:38:19 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 68235-08-2 for ; Mon, 5 Jun 2006 16:38:11 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from davinci.ethosmedia.com (server227.ethosmedia.com [209.128.84.227]) by postgresql.org (Postfix) with ESMTP id C7E519FA5C8 for ; Mon, 5 Jun 2006 16:38:10 -0300 (ADT) X-EthosMedia-Virus-Scanned: no infections found Received: from [64.81.245.111] (account josh@agliodbs.com HELO [192.168.1.27]) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 9529754 for pgsql-students@postgresql.org; Mon, 05 Jun 2006 12:41:20 -0700 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: pgsql-students@postgresql.org Subject: Hashing Distinct/pgFoundry project? Date: Mon, 5 Jun 2006 12:37:44 -0700 User-Agent: KMail/1.8 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200606051237.44883.josh@agliodbs.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/23 X-Sequence-Number: 26 Beth, Simon, Given that Hashing DISTINCT is a patch on the main PostgreSQL code, does it make sense to set up a pgfoundry project for it? Or should you just use hackers/patches? I'm OK with it either way, just wanted to make sure that you had reasons for wanting to use pgFoundry. -- --Josh Josh Berkus PostgreSQL @ Sun San Francisco