From: | Rodrigo Barboza <rodrigombufrj(at)gmail(dot)com> |
---|---|
To: | Igor Neyman <ineyman(at)perceptron(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: How do I know my table is bloated? |
Date: | 2013-05-30 16:03:47 |
Message-ID: | CANs8QJb7r6Q98r3NFs7MFr1QaifRs9JZ+KMaCy==A63tX1dPeQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I have some tables that I do a lot of updates, deletes and inserts.
So I am worried that my cluster can grow up to a huge size...
The best option would be to create a scheduled process to check if it is
bloated and if so, reindex?
On Thu, May 30, 2013 at 12:17 PM, Igor Neyman <ineyman(at)perceptron(dot)com>wrote:
>
>
> From: Rodrigo Barboza [mailto:rodrigombufrj(at)gmail(dot)com]
> Sent: Thursday, May 30, 2013 11:10 AM
> To: Igor Neyman
> Cc: pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] How do I know my table is bloated?
>
> Well, so I need to do reindex frequentely in database? Is that right?
> Or should I use cluster, as David said?
> How frequently should I do this operation?
>
> ---------------------
>
> Not necessarily.
> If there is no table or index bloat, which you should be able to check
> first, - why bother?
>
> Normally autovacuum does pretty good job even with default configuration
> parameters.
> If not, you could start with adjusting autovacuum parameters.
> And reindex only as a last resort, when your index size grows
> "uncontrollably".
>
> Igor Neyman
>
From | Date | Subject | |
---|---|---|---|
Next Message | Igor Neyman | 2013-05-30 16:35:32 | Re: How do I know my table is bloated? |
Previous Message | Igor Neyman | 2013-05-30 15:17:33 | Re: How do I know my table is bloated? |