Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TaaxI-0002zH-O0 for pgsql-admin@postgresql.org; Mon, 19 Nov 2012 23:40:44 +0000 Received: from nm14-vm1.bullet.mail.ne1.yahoo.com ([98.138.91.38]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TaaxH-0001HT-0p for pgsql-admin@postgresql.org; Mon, 19 Nov 2012 23:40:44 +0000 Received: from [98.138.226.178] by nm14.bullet.mail.ne1.yahoo.com with NNFMP; 19 Nov 2012 23:40:42 -0000 Received: from [98.138.89.253] by tm13.bullet.mail.ne1.yahoo.com with NNFMP; 19 Nov 2012 23:40:42 -0000 Received: from [127.0.0.1] by omp1045.mail.ne1.yahoo.com with NNFMP; 19 Nov 2012 23:40:42 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 115282.55225.bm@omp1045.mail.ne1.yahoo.com Received: (qmail 11439 invoked by uid 60001); 19 Nov 2012 23:40:42 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1353368442; bh=+9DSwjABa6PfqlkHqkNyWGRjxQWFomeHws/nnL/O1uM=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=anuGGqXCxoaaiNMY7dy4Nh9nHplzFYZ65ndSXazsl5gnDEC7nOB2UX13nTWM8Ifj/aAK0mwJkwSx2LdUjON8608NGB+c2WrbrGaDFSM5JS8nsxILkomJwp9Sd5cG7UrikhRBGlDkdzJr6xhKPuMhha3QHIjd8rdKgXoqrwmIwoY= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ZQB3dZogvmV/RIpno5XRrpW9i5F2urXkw4Udn+TlLZjv5NHLxGoLLcTD/Iidz5RzuHYXIGcYa/FaUxuBm6HIGkNj9lxeZYrHDMAR2n1uBU1j6nbCS+hSmIgeC9OytV03ww1LIc3qfW7l9TmRuXtztDDJfSx6Wj1cAkoLL6iNw58=; X-YMail-OSG: kPYGr1EVM1nBI9TAAOgkaxpGt9JI8B0jeilpCDbQFN_YewX BTefd2aE_pMjpjnc1BI33UP3nMK3dqgiq4wrBynE0qKnf_1kFNCShtpa79a0 SGXDumeRUkqSKrFGYzleVHZIg9dflDymr1uIsOSGTiy3c5X7gyiaiBuvC4L6 RprqD7kg8JU8XaDfHG0jO2CeP55Qc15ejteqa668oJlOErvuWml.Dye5pR1i 4hIqqwSQVFKk0qfruQ5KTwbAE9gEgzpskjPa0Of_8qNeV8zKTuHHGjWjBYbK I9fE0xD3vtqDLTJdt3Ms21Gan89MK3iBcZ.QzatQd4kelMRuo1OGBu.Z8ke6 sZ4VXpQsc6BGfV.ct4DLvZExKQUUkl1DzIqYi58FY2kRsnXGflk.A1lqAWTq hjZKS.PXdGrU1WkYCg8mHRyAvG4QBRSl1a5Ca66XT9V768we_1NpZ2P1NJR5 OX33tNW_NhleXM0Gg4G9Ln_fat4atifY9UG0dt7e5w3Xa8NP2BixtgRKGSA- - Received: from [199.9.251.45] by web125903.mail.ne1.yahoo.com via HTTP; Mon, 19 Nov 2012 15:40:41 PST X-Rocket-MIMEInfo: 001.001, U2FtdWVsIC0tCgoKCj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo.IEZyb206IFNhbXVlbCBTdGVhcm5zIDxTU3RlYXJuc0BpbnRlcm5vZGUuY29tLmF1Pgo.VG86ICJwZ3NxbC1hZG1pbkBwb3N0Z3Jlc3FsLm9yZyIgPHBnc3FsLWFkbWluQHBvc3RncmVzcWwub3JnPiAKPlNlbnQ6IE1vbmRheSwgTm92ZW1iZXIgMTksIDIwMTIgMTo1OSBQTQo.U3ViamVjdDogW0FETUlOXSBSZXNvbHZpbmcgSW5kZXggQmxvYXQKPiAKPgo.PC4uLj4KPgo.QW55IGlkZWFzIG9uIGhvdyB0byByZXNvbHZlPwo.wqABMAEBAQE- X-Mailer: YahooMailWebService/0.8.126.470 References: Message-ID: <1353368441.76758.YahooMailNeo@web125903.mail.ne1.yahoo.com> Date: Mon, 19 Nov 2012 15:40:41 -0800 (PST) From: Greg Williamson Reply-To: Greg Williamson Subject: Re: Resolving Index Bloat To: "pgsql-admin@postgresql.org" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Pg-Spam-Score: 0.9 (/) X-Archive-Number: 201211/104 X-Sequence-Number: 40349 Samuel --=0A=0A=0A=0A>________________________________=0A> From: Samuel Ste= arns =0A>To: "pgsql-admin@postgresql.org" =0A>Sent: Monday, November 19, 2012 1:59 PM=0A>Subje= ct: [ADMIN] Resolving Index Bloat=0A> =0A>=0A><...>=0A>=0A>Any ideas on how= to resolve?=0A>=A0=0A=0A=0AI have custody of one database that is fairly s= mall but subjected to lots of updated, inserts and deletes, and that databa= se shows bloat that we have to knock down hourly or performance tanks.=0A= =0AThis is on postgres 9.1 so I am not sure how much translates to earlier = versions.=0A=0AWe ran ""REINDEX" hourly for a while; we currently use a han= d rolled script that reindexes each regular index and does a dance to reind= ex primary keys and constraints. I could email it to you but as I said, not= sure how much would work.=0A=0AThe straight REINDEX did work 99% of the ti= me, with very occasional reports of failures, never repeated. The hand roll= ed version is a bit safer and a little less intrusive.=0A=0AHTH,=0A=0AGreg = Williamson