Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 2CE869FB36C for ; Sun, 27 May 2007 12:53:47 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 99203-09 for ; Sun, 27 May 2007 12:53:43 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 67E249FB35D for ; Sun, 27 May 2007 12:53:43 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 1FCDE56459; Sun, 27 May 2007 10:53:40 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Sun, 27 May 2007 10:53:38 -0500 Date: Sun, 27 May 2007 10:53:38 -0500 From: "Jim C. Nasby" To: PFC Cc: "pgsql-performance@postgresql.org" Subject: Re: Feature suggestion : FAST CLUSTER Message-ID: <20070527155338.GM92628@nasby.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tT3UgwmDxwvOMqfu" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 6.1-RELEASE-p10 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.13 (2006-08-11) X-Hashcash: 1:20:070527:lists@peufeu.com::4QuyevDvHfSuDSVu:00etE X-Hashcash: 1:20:070527:pgsql-performance@postgresql.org::j6TnUvBrdH+DbXjr:00000 0000000000000000000000005jkf X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/559 X-Sequence-Number: 24949 --tT3UgwmDxwvOMqfu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 22, 2007 at 09:29:00AM +0200, PFC wrote: > This does not run a complete sort on the table. It would be about as=20 > fast as your seq scan disk throughput. Obviously, the end result is not= as=20 > good as a real CLUSTER since the table will be made up of several ordere= d =20 > chunks and a range lookup. Therefore, a range lookup on the clustered =20 > columns would need at most N seeks, versus 1 for a really clustered table= =2E =20 > But it only scans the table once and writes it once, even counting index = =20 > rebuild. Do you have any data that indicates such an arrangement would be substantially better than less-clustered data? --=20 Jim Nasby decibel@decibel.org EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) --tT3UgwmDxwvOMqfu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iD8DBQFGWamCdO30qud8SkgRAiBxAJ0WV2p7FhFqgMtrdJtflUNDIQv2kwCg3rSg q09VHkSK+0DAk+f7gysBN5A= =rnse -----END PGP SIGNATURE----- --tT3UgwmDxwvOMqfu--