From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jeffrey Baker <jwbaker(at)acm(dot)org>, Scott Marlowe <scott(dot)marlowe(at)ihs(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Subject: bool / vacuum full bug followup |
Date: | 2002-06-02 21:02:17 |
Message-ID: | 200206022102.g52L2Hp28149@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> Jeffrey Baker <jwbaker(at)acm(dot)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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-06-02 21:34:05 | Re: select from function |
Previous Message | Bruce Momjian | 2002-06-02 20:28:26 | MVCC and MS-SQL comparison |