Skip site navigation (1) Skip section navigation (2)

Re: Concurrent Reindex on Primary Key for large table

From: "Igor Neyman" <ineyman(at)perceptron(dot)com>
To: "rverghese" <riyav(at)hotmail(dot)com>,<pgsql-sql(at)postgresql(dot)org>
Subject: Re: Concurrent Reindex on Primary Key for large table
Date: 2012-02-10 14:41:38
Message-ID: F4C27E77F7A33E4CA98C19A9DC6722A208BEA92B@EXCHANGE.corp.perceptron.com (view raw or flat)
Thread:
Lists: pgsql-sql
> -----Original Message-----
> From: rverghese [mailto:riyav(at)hotmail(dot)com]
> Sent: Thursday, February 09, 2012 12:49 PM
> To: pgsql-sql(at)postgresql(dot)org
> Subject: Re: Concurrent Reindex on Primary Key for large table
> 
> Thanks! That worked.
> 
> Any thoughts about containing index bloat. I thought the autovac would
> clean it up a bit more. Would any tweaks to my settings improve
autovac
> performance? I am still doing a couple of concurrent reindexes per
week
> otherwise performance degrades over a couple of days.
> 
> Thanks
> RV
> 
> --
> View this message in context:
> http://postgresql.1045698.n5.nabble.com/Concurrent-Reindex-on-Primary-
> Key-for-large-table-tp5467243p5470216.html
> Sent from the PostgreSQL - sql mailing list archive at Nabble.com.

Did you try to make autovacuum "more aggressive" like lowering
autovacuum_vacuum_threshold from 20000?

Regards, 
Igor Neyman

In response to

pgsql-sql by date

Next:From: Oliveiros d'Azevedo CristinaDate: 2012-02-10 15:33:09
Subject: Re: update column
Previous:From: rvergheseDate: 2012-02-09 17:48:53
Subject: Re: Concurrent Reindex on Primary Key for large table

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group