Re: On-disk size of db increased after restore - Mailing list pgsql-general

From Tom Lane
Subject Re: On-disk size of db increased after restore
Date
Msg-id 21406.1283521260@sss.pgh.pa.us
Whole thread Raw
In response to Re: On-disk size of db increased after restore  (Devrim GÜNDÜZ <devrim@gunduz.org>)
Responses Re: On-disk size of db increased after restore  (Devrim GÜNDÜZ <devrim@gunduz.org>)
List pgsql-general
Devrim =?ISO-8859-1?Q?G=DCND=DCZ?= <devrim@gunduz.org> writes:
> On Thu, 2010-09-02 at 13:22 -0400, Tom Lane wrote:
>> Devrim, have you identified yet which tables have the bloat?  Are they
>> the ones with tweaked autovacuum parameters?

> That's it.

> On prod server, that table consumes 50 GB disk space, and on the backup
> machine, it uses 148 GB. I applied custom autovac settings only to that
> table.

> This is 8.4.4 btw...

OK, so the bug is fixed, but you still have fillfactor = 0 on the
affected table.

> So, what should I do now?

Explicitly reset the table's fillfactor to default (100), then
you'll need to CLUSTER or VACUUM FULL or something.

            regards, tom lane

pgsql-general by date:

Previous
From: "A. Kretschmer"
Date:
Subject: Re: alter column to inet get error.
Next
From: "Daniel Wagner"
Date:
Subject: Problems (bug?) with the Postgres 8.4.4 optimizer, 2nd try