Hi, Thank you for the info. I am doing the reindex for an individual index. And i am doing this in the live server and apps are connecting to it at the same time. Is this not correct?
I am new to postgres. Kindly brief me the steps which i need to follow. Prasad On Fri, Apr 1, 2011 at 1:28 PM, Jerry Sievers <[email protected]>wrote: > Rajendra prasad <[email protected]> writes: > > > Hi, > > > > I have 50 GB data base folder for postgres. Out of 50 GB 20 GB has > > been occupied by 8 indexes of a single table by growing upto 2 GB > > each. I googled and got the info that reindex will help brining back > > the actual size of the index. But the disk has only 4 GB left . Due to > > this, when i run reindex it is getting almost full. I don't know > > exactly why it is growing like that during reindex. Due to this i am > > not able to complete the reindex and see if i get back the disk > > spacce. Please suggest me a good solution and the way that i am doing > > is logical or not. > > Did you try reindexing each index individually? > > The old index files will be dropped in that case upon completion of each > command if you are running autocommit. Less transient disk space demand > by that strategy. > > Even more disk friendly is just to drop/create the indexes. > > Since you can't reindex without blocking anyway, I assume you are clear > of concurrency issues to prevent using this advice (apps down and/or > quiescent). > > -- > Jerry Sievers > Postgres DBA/Development Consulting > e: [email protected] > p: 305.321.1144 >
