Skip site navigation (1) Skip section navigation (2)

Re: Index bloat problem?

From: Michael Guerin <guerin(at)rentec(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Bill Chandler <billybobc1210(at)yahoo(dot)com>,pgsql-perform <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Index bloat problem?
Date: 2005-04-21 18:24:57
Message-ID: 4267EFF9.2000908@rentec.com (view raw or flat)
Thread:
Lists: pgsql-performance
>>Is 
>>this a common issue among all RDBMSs or is it
>>something that is PostgreSQL specific?  
>>    
>>
>
>Speaking from experience, this sort of thing affects MSSQL as well, although 
>the maintenance routines are different.
>
>  
>
Yes, this is true with MSSQL too, however sql server implements a defrag 
index that doesn't lock up the table..

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_dbcc_30o9.asp

"DBCC INDEXDEFRAG can defragment clustered and nonclustered indexes on 
tables and views. DBCC INDEXDEFRAG defragments the leaf level of an 
index so that the physical order of the pages matches the left-to-right 
logical order of the leaf nodes, thus improving index-scanning performance.

....Every five minutes, DBCC INDEXDEFRAG will report to the user an 
estimated percentage completed. DBCC INDEXDEFRAG can be terminated at 
any point in the process, and *any completed work is retained.*"

-michael


In response to

Responses

pgsql-performance by date

Next:From: Josh BerkusDate: 2005-04-21 18:28:43
Subject: Re: Index bloat problem?
Previous:From: Chris BrowneDate: 2005-04-21 17:51:18
Subject: Re: How can an index be larger than a table

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group