| From: | Jayadevan M <maymala(dot)jayadevan(at)gmail(dot)com> |
|---|---|
| To: | harish Reddy <harishr536(at)gmail(dot)com> |
| Cc: | "pgsql-sql(at)postgresql(dot)org" <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: Fwd: Regarding change in the size of database |
| Date: | 2016-10-26 13:37:53 |
| Message-ID: | CAFS1N4iJfQSECDr01Nw-NwO=adfV8qwPDoDtS-Jv6OeKLMEb+A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Wed, Oct 26, 2016 at 10:31 AM, harish Reddy <harishr536(at)gmail(dot)com> wrote:
>
> ---------- Forwarded message ----------
> From: harish Reddy <harishr536(at)gmail(dot)com>
>
> Subject: Regarding change in the size of database
>
>
>
> Hi Sir,
>
> I had my PostgreSQL DB in Procduction environment was about *45GB* and
> when I taken it's dump and restored into my local environment it was about*
> 20GB* . I want to know what is going wrong and when i had observed it is
> differing to a single table also so could you suggest us what is the issue
> and possible solution and in a day it has incresed over 1 GB again
> suggest me where can i get the solution
>
> Thanks and Regards
> Harish Reddy
>
> Probably there was table bloat in your production environment. When you
restored, the bloat would have disappeared. 20 GB is the actual size. Read
details about bloat here
http://dba.stackexchange.com/questions/126258/what-is-table-bloating-in-databases
Proper vacuum is the solution.
Regards,
Jayadevan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | harish Reddy | 2016-10-26 16:21:10 | Re: Fwd: Regarding change in the size of database |
| Previous Message | harish Reddy | 2016-10-26 05:01:08 | Fwd: Regarding change in the size of database |