Re: Indexes and Tables: Growth and Treatment

From: Thomas F(dot)O'Connell <tfo(at)sitening(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgreSQL(dot)org
Subject: Re: Indexes and Tables: Growth and Treatment
Date: 2004-07-14 00:03:33
Message-ID: 3EDA038A-D529-11D8-A7DD-000D93AE0944@sitening.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Jul 13, 2004, at 6:58 PM, Tom Lane wrote:

> Try hourly vacuums. If that doesn't stem the tide, make it more often
> (or try autovacuum).

I will try autovacuum.

> Also make sure that your FSM settings are large
> enough; if they're not then no amount of plain vacuuming will keep you
> out of trouble.

I was just reading up on FSM settings today. In fact, here's the output
of a recent VACUUM VERBOSE:

INFO: free space map: 1000 relations, 11599 pages stored; 100064 total
pages needed
DETAIL: Allocated FSM size: 1000 relations + 20000 pages = 178 kB
shared memory.

So clearly we need to increase max_fsm_pages. How is this related to
vacuuming? And is it related at all to index growth?

> With sufficiently frequent plain vacuums you really shouldn't need
> vacuum full at all.

So is the only benefit to that the extreme optimizations of disk space
it undertakes? Is there any point at which the extra compacting
actually results in a performance enhancement?

> I can't recommend an analyze frequency on what you've told us.

What more information would you need to make a recommendation?

Thanks for all the tips!

-tfo

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Mike G 2004-07-14 01:37:15 Re: function returning a readable representation of a number
Previous Message Tom Lane 2004-07-13 23:58:24 Re: Indexes and Tables: Growth and Treatment (Modified by Thomas F. O'Connell)