Re: Resolving Index Bloat - Mailing list pgsql-admin

From Samuel Stearns
Subject Re: Resolving Index Bloat
Date
Msg-id CBAC86BE623FDB4E8B6225471691724291E1C8DC@EXCHMBX-ADL6-01.staff.internode.com.au
Whole thread Raw
In response to Re: Resolving Index Bloat  (Greg Williamson <gwilliamson39@yahoo.com>)
List pgsql-admin
Thanks, Greg.

I may look at running a scheduled REINDEX.

Sam


-----Original Message-----
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Greg Williamson
Sent: Tuesday, 20 November 2012 10:11 AM
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Resolving Index Bloat

Samuel --



>________________________________
> From: Samuel Stearns <SStearns@internode.com.au>
>To: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
>Sent: Monday, November 19, 2012 1:59 PM
>Subject: [ADMIN] Resolving Index Bloat
>
>
><...>
>
>Any ideas on how to resolve?
> 


I have custody of one database that is fairly small but subjected to lots of updated, inserts and deletes, and that
databaseshows bloat that we have to knock down hourly or performance tanks. 

This is on postgres 9.1 so I am not sure how much translates to earlier versions.

We ran ""REINDEX" hourly for a while; we currently use a hand rolled script that reindexes each regular index and does
adance to reindex primary keys and constraints. I could email it to you but as I said, not sure how much would work. 

The straight REINDEX did work 99% of the time, with very occasional reports of failures, never repeated. The hand
rolledversion is a bit safer and a little less intrusive. 

HTH,

Greg Williamson


--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin


pgsql-admin by date:

Previous
From: Pat Heuvel
Date:
Subject: Re: No databases visible on pg 8.3 server
Next
From: Shams Khan
Date:
Subject: How to check history of sequences and constraints (version 9.1)