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

From Bruce Momjian
Subject Re: Subject: bool / vacuum full bug followup
Date
Msg-id 200206022102.g52L2Hp28149@candle.pha.pa.us
Whole thread Raw
In response to Re: Subject: bool / vacuum full bug followup  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Tom Lane wrote:
> 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.

One subtle point is that TOAST space and HEAP space used by a table are
not shared, meaning if you have TOAST space free, that can't be used for
HEAP storage, and via versa.  Of course, a FULL vacuum frees all unused
space.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

pgsql-general by date:

Previous
From: Bruce Momjian
Date:
Subject: MVCC and MS-SQL comparison
Next
From: Bruce Momjian
Date:
Subject: Re: select from function