| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeffrey Baker <jwbaker(at)acm(dot)org> |
| Cc: | 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-05-03 04:20:44 |
| Message-ID: | 4028.1020399644@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul M Foster | 2002-05-03 04:29:38 | Re: Fwd: Postfix Relay Hub SMTP server: errors from postgresql.org[64.49.215.8] |
| Previous Message | Jeffrey Baker | 2002-05-03 03:58:40 | Re: Subject: bool / vacuum full bug followup |