Re: Subject: bool / vacuum full bug followup - Mailing list pgsql-general

From Tom Lane
Subject Re: Subject: bool / vacuum full bug followup
Date
Msg-id 4028.1020399644@sss.pgh.pa.us
Whole thread Raw
In response to Re: Subject: bool / vacuum full bug followup  (Jeffrey Baker <jwbaker@acm.org>)
Responses Re: Subject: bool / vacuum full bug followup
Re: Subject: bool / vacuum full bug followup
List pgsql-general
Jeffrey Baker <jwbaker@acm.org> writes:
> Well, if the table has an associated TOAST table, it is possible
> that it will suddenly start growing out of control, and nothing you
> can do with VACUUM will help.  The TOAST system has a free space map
> (FSM) with some default number of pages it can track.  If you exceed
> this number, it will become completely unable to reclaim space.

That's a gross misstatement.

If you have more pages with free space than the FSM can track, it will
forget about the ones with the least free space (at least until the next
vacuum tries to reload the info).  This will very possibly lead to table
growth over time, but it's hardly the same as "completely unable to
reclaim space".

BTW, TOAST has nothing to do with this.  Space in main tables and
toast tables is tracked alike.

            regards, tom lane

pgsql-general by date:

Previous
From: Jeffrey Baker
Date:
Subject: Re: Subject: bool / vacuum full bug followup
Next
From: Paul M Foster
Date:
Subject: Re: Fwd: Postfix Relay Hub SMTP server: errors from postgresql.org[64.49.215.8]