From: | Aditya <aditya(at)grot(dot)org> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | sfpug(at)postgresql(dot)org |
Subject: | Re: Freebsd vs linux and hardware question |
Date: | 2003-09-22 17:42:14 |
Message-ID: | 20030922174214.GA94115@mighty.grot.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | sfpug |
On Mon, Sep 22, 2003 at 10:24:29AM -0700, Josh Berkus wrote:
> Dror,
>
> > But actually one of the big problems was solved when we ran VACUUM FULL
> > on a problematic table. It shrank from 100 Megs to 6 Megs which on a
> > local disk isn't as big a problem as on a NAS.
> >
> > We're also now running VACUUM ANALYZE on the table every five minutes
> > instead of once a day and that helps too.
>
> What is your setting for max_fsm_pages? Have you compared it against the
> results of logged VACUUM VERBOSE? And I'd be surprised if running VACUUM
> ANALYZE ever 5 minutes is necessary ... VACUUM should do, with ANAYLZE maybe
> once a day, unless your users are big on changing a large % of rows at once.
these are the defaults in the config that we're using:
#max_fsm_relations = 100 # min 10, fsm is free space map
#max_fsm_pages = 10000 # min 1000, fsm is free space map
FWIW, there are several thousand rows that get updated every few minutes.
I'll let Dror answer as to why VACUUM ANALYZE vs. VACUUM alone.
> Finally, what about REINDEX?
Because we have to remove all those addl. deleted/updated rows...
Aditya
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2003-09-22 17:51:51 | Re: Freebsd vs linux and hardware question |
Previous Message | Josh Berkus | 2003-09-22 17:24:29 | Re: Freebsd vs linux and hardware question |