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 DF6425E46F8 for ; Thu, 26 Aug 2004 19:01:58 -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 36240-10 for ; Thu, 26 Aug 2004 22:01:51 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id DCFBB5E46F2 for ; Thu, 26 Aug 2004 19:01:50 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i7QM1oLs039915 for ; Thu, 26 Aug 2004 22:01:50 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i7QLf25N033373 for pgsql-performance@postgresql.org; Thu, 26 Aug 2004 21:41:02 GMT From: Mischa Sandberg Reply-To: ischamay.andbergsay@activestateway.com User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 X-Newsgroups: comp.databases.postgresql.performance Subject: Re: Equivalent praxis to CLUSTERED INDEX? References: <6BCB9D8A16AC4241919521715F4D8BCE475B39@algol.sollentuna.se> <1093553043.349.171.camel@vulture.corp.neopolitan.com> In-Reply-To: <1093553043.349.171.camel@vulture.corp.neopolitan.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Lines: 17 Message-ID: Date: Thu, 26 Aug 2004 21:41:04 GMT To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.1 tagged_above=0.0 required=5.0 tests=NO_DNS_FOR_FROM X-Spam-Level: * X-Archive-Number: 200408/422 X-Sequence-Number: 8058 J. Andrew Rogers wrote: > On Thu, 2004-08-26 at 12:30, Magnus Hagander wrote: >>IIRC, SQL Server always creates clustered indexes by default for primary >>keys. > > That would surprise me actually. Yaz, it should. It doesn't ALWAYS create clustered (unique) index for primary keys, but clustered is the default if you just specify CREATE TABLE Foo (col1, ... ,PRIMARY KEY(col1, ...) ) Saying PRIMARY KEY NONCLUSTERED(...) is how you override the default. ((Weird to be discussing so much MSSQL here))