Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1T081v-0007fU-Dh for pgsql-performance@postgresql.org; Sat, 11 Aug 2012 09:30:47 +0000 Received: from andy.depesz.com ([88.198.47.100] helo=depesz.com) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1T081t-0003Ib-MW for pgsql-performance@postgresql.org; Sat, 11 Aug 2012 09:30:46 +0000 Received: from andy.depesz.com ([88.198.47.100] helo=depesz.com) by depesz.com with esmtpa (Exim 4.80) (envelope-from ) id 1T081r-0002Vh-5l; Sat, 11 Aug 2012 11:30:43 +0200 Date: Sat, 11 Aug 2012 11:30:42 +0200 From: hubert depesz lubaczewski To: Strahinja =?utf-8?B?S3VzdHVkacSH?= Cc: pgsql-performance@postgresql.org Subject: Re: Index Bloat Problem Message-ID: <20120811093042.GA3042@depesz.com> Reply-To: depesz@depesz.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Pg-Spam-Score: -0.0 (/) X-Archive-Number: 201208/65 X-Sequence-Number: 47603 On Sat, Aug 11, 2012 at 12:15:11AM +0200, Strahinja Kustudić wrote: > Is there a way to make the autovacuum daemon more aggressive, since I'm not > exactly sure how to do that in this case? Would that even help? Is there > another way to remove this index bloat? http://www.depesz.com/index.php/2011/07/06/bloat-happens/ Best regards, depesz -- The best thing about modern society is how easy it is to avoid contact with it. http://depesz.com/