| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Philip Warner" <pjw(at)rhyme(dot)com(dot)au> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: toast table growing indefinitely? Known |
| Date: | 2002-12-02 20:14:46 |
| Message-ID: | 00c801c29a3f$7630ec10$6500a8c0@internal |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Good call; they are still default (10000 pages) and we are seeing 26000
> pages per day being updated:
>
> NOTICE: Removed 102226 tuples in 26002 pages.
> CPU 2.02s/1.87u sec elapsed 69.85 sec.
> NOTICE: Pages 201819: Changed 26128, Empty 0; Tup 315227: Vac 102226,
Keep
> 0, UnUsed 393793.
> Total CPU 9.57s/3.07u sec elapsed 189.32 sec.
>
> I've increased the value to 40000 since we have much busier days, and I'll
> se what happens.
Hang on - so when vacuum runs it knows exactly how many pages it cleaned up
but if the fsm value is low, it doesn't help? Why don't we just
automaticlaly set the FSM value to the max that vacuum has to clean up? Why
don't we introduce: max_fsm_pages = auto or something?
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2002-12-02 20:25:34 | Re: 7.4 Wishlist |
| Previous Message | Szima Gábor | 2002-12-02 20:07:04 | Re: numeric to text (7.3) |