Re: Giant TOAST tables due to many almost empty pages

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Rumko <rumcic(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Giant TOAST tables due to many almost empty pages
Date: 2010-05-14 18:02:02
Message-ID: 20073.1273860122@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Rumko <rumcic(at)gmail(dot)com> writes:
> On Friday 14. of May 2010 19:29:44 Tom Lane wrote:
>> Hmm, do both of the toast tables with bloat problems have
>> "{autovacuum_enabled=false}" ?

> Yeah, but also many others that don't have the problem.

Hmm, well I can reproduce the problem after doing
alter table foo set (toast.autovacuum_enabled = false);

Haven't investigated exactly why yet, but I imagine that the presence of
a nonnull reloptions setting for a toast table is confusing the code
that determines the default fillfactor.

As a workaround, I'd suggest getting rid of that:
alter table foo reset (toast.autovacuum_enabled);
and then doing VACUUM FULL on the bloated table.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2010-05-14 19:15:46 Re: pg_restore ignores -C when using a restore list -L
Previous Message Rumko 2010-05-14 17:38:08 Re: Giant TOAST tables due to many almost empty pages