X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 66C8C5E3F15 for ; Sun, 29 Aug 2004 15:58:23 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 22196-07 for ; Sun, 29 Aug 2004 18:58:20 +0000 (GMT) Received: from davinci.ethosmedia.com (server226.ethosmedia.com [209.128.84.226]) by svr1.postgresql.org (Postfix) with ESMTP id 0CC4F5E3631 for ; Sun, 29 Aug 2004 15:58:20 -0300 (ADT) Received: from [63.195.55.98] (account josh@agliodbs.com HELO temoku.sf.agliodbs.com) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 6220188; Sun, 29 Aug 2004 11:59:37 -0700 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: ischamay.andbergsay@activestateway.com Subject: Re: Equivalent praxis to CLUSTERED INDEX? Date: Sun, 29 Aug 2004 11:59:01 -0700 User-Agent: KMail/1.6.2 Cc: pgsql-performance@postgresql.org References: <200408261818.i7QIIrr09640@candle.pha.pa.us> <200408261132.30732.josh@agliodbs.com> <3csXc.56326$X12.25148@edtnps84> In-Reply-To: <3csXc.56326$X12.25148@edtnps84> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200408291159.01205.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/427 X-Sequence-Number: 8063 Mishca, > Ummm ... not quite. In MSSQL/Sybase/Oracle, a clustered index maintains > its space saturation as part of each update operation. High activity > does indeed result in less-full pages (typically 60-80% full for tables > with heavy deletions or rowsize changes). To bring the percentage back > up, you run DBCC INDEXDEFRAG, which also does what you'd expect of a > normal file defragmenter -- put related disk pages together on the platter. Sure, it does now, which is a nice thing. It didn't in the first version (6.5) where this cluster maint needed to be done manually and asynchronously, as I recall. > As for SQL Server being a 'single-user database' ... ummm ... no, I > don't think so. Hmmm ... perhaps it would be better if I said "serial-only database". MSSQL (like earlier versions of Sybase) handles transactions by spooling everything out to a serial log, effectively making all transcations SERIAL isolation. This has some significant benefits in performance for OLAP and data warehousing, but really kills you on high-concurrency transaction processing. > I'm REALLY happy to be shut of the Microsoft world, but > MSSQL 7/2000/2005 is a serious big DB engine. It also has some serious > bright heads behind it. They hired Goetz Graefe and Paul (aka Per-Ake) > Larsen away from academia, and it shows, in the join and aggregate > processing. I'll be a happy camper if I manage to contribute something > to PG that honks the way their stuff does. Happy to discuss, too. Yeah, they also have very speedy cursor handling. I can do things with cursors in MSSQL that I wouldn't consider with other DBs. Not that that makes up for the lack of other functionality, but it is nice when you need it. -- --Josh Josh Berkus Aglio Database Solutions San Francisco