At 12:37 AM 2/12/2002 -0500, Tom Lane wrote:
Good call; they are still default (10000 pages) and we are seeing 26000 pages per day being updated:If you're seeing bloat while using plain (not full) vacuums, my guess would be that you need to enlarge the FSM parameters in postgresql.conf.
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.
Is there any way (other than VACUUM FULL) to recover the current lost space?
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 03 5330 3172 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
