Looking for a fix to index bloat
We are suffering from the same issue that is described in this email thread http://archives.postgresql.org/pgsql-general/2005-07/msg00486.php.
I don't know if this is the appropriate place to make this request, so if not, please forgive me. However, in our particular case, we don't have enough disk space nor money to allow the indexes to grow to a steady state. We are willing to pay someone to implement the suggested fix described in the above thread on version 8.0.3. If interested, please respond to this email with your contact information and a rough idea of how much it would cost and how long it would take to get the job done.
Thank you for your consideration.
Brent
bfraci@aol.com wrote on
Tuesday, February 28, 2006 7:13 AM
We are suffering from the same issue that is described in this email thread
http://archives.postgresql.org/pgsql-general/2005-07/msg00486.php.I don't know if this is the appropriate place to make this request, so if
not, please forgive me. However, in our particular case, we don't have enough
disk space nor money to allow the indexes to grow to a steady state.
This isn't what you asked for, but if you can afford a modest amount of
downtime you could always drop/recreate the indexes.
-Roger
Import Notes
Resolved by subject fallback
On Tue, Feb 28, 2006 at 10:13:14AM -0500, bfraci@aol.com wrote:
We are suffering from the same issue that is described in this email thread http://archives.postgresql.org/pgsql-general/2005-07/msg00486.php.
I don't know if this is the appropriate place to make this request, so if not, please forgive me. However, in our particular case, we don't have enough disk space nor money to allow the indexes to grow to a steady state. We are willing to pay someone to implement the suggested fix described in the above thread on version 8.0.3. If interested, please respond to this email with your contact information and a rough idea of how much it would cost and how long it would take to get the job done.
Have you tried vacuuming more frequently?
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
Have you tried vacuuming more frequently?
Yes, we vacuum every 45-60 minutes. We boarder on having a vacuum running continuously vacuuming some table in the database.
Brent
This isn't what you asked for, but if you can afford a modest amount of downtime you could always drop/recreate the indexes.
Unfortunately, we cannot afford any down time. That is why we are looking to pay someone to help us implement Tom Lane's suggested solution.
Brent