| From: | Ben Chobot <bench(at)silentmedia(dot)com> |
|---|---|
| To: | Meena_Ramkumar <winmeena_ramkumar(at)yahoo(dot)co(dot)in> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Postgres DB maintainenance - vacuum and reindex |
| Date: | 2010-03-16 17:06:41 |
| Message-ID: | 5F413149-F922-4CC4-952E-CBDC40DBD62F@silentmedia.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Autovacuum is your friend for minimal downtime. It is configurable to let you adjust how invasive it will be, and you can have different settings per table if you wish.
As for the reindex, why do you think you will be reindexing regularly?
On Mar 15, 2010, at 10:30 PM, Meena_Ramkumar wrote:
>
> How to run vacuumdb and reindex for Postgres DB in a non-stop server? Will it
> be made without shutting the server? If so, then what will be performance
> degradation percentage?
> --
> View this message in context: http://old.nabble.com/Postgres-DB-maintainenance---vacuum-and-reindex-tp27913694p27913694.html
> Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
>
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ing. Marcos Ortiz Valmaseda | 2010-03-16 17:29:15 | Re: Postgres DB maintainenance - vacuum and reindex |
| Previous Message | Scott Marlowe | 2010-03-16 16:58:08 | Re: Postgres DB maintainenance - vacuum and reindex |