>
> AS for the process pool ... there are two camps here ... if you use
> threads, when one threads crashes the server, the server is done. With
> forking,if one backend dies, the server is still running ... in a 24x7
> shop, I'd rather the solution that doesn't die cause JoeBlow down the hall
>
Matthew Arnison wrote:
>
> the bloat is a big problem. i just checked it again, and the db has
> balloooned to 20 megs again, with i think 2650 unused pages. this is after
> vacuuming it last night. i guess we need to setup the vacuum script to run
> every hour. i am worried about this locking ou
more immediate solution out
there for you. ;)
-Brian
>Date: Fri, 14 Apr 2000 16:29:23 +1000 (EST)
>From: Matthew Arnison <[EMAIL PROTECTED]>
>To: Ed Loehr <[EMAIL PROTECTED]>
>cc: [EMAIL PROTECTED], Rabble-Rouser <[EMAIL PROTECTED]>, Manse
Jacobi <[EMAIL PROTEC
the bloat is a big problem. i just checked it again, and the db has
balloooned to 20 megs again, with i think 2650 unused pages. this is after
vacuuming it last night. i guess we need to setup the vacuum script to run
every hour. i am worried about this locking out users during the
vacuuming, alth
Matthew Arnison wrote:
>
> three times now this week (on two different servers) the raw database on
> disk has ballooned in size, from about 10 megs to 50 megs in two cases,
> and from about 10 megs to 250 megs in another case.
>
> a VACUUM VERBOSE ANALYZE; cleans it back down to the proper size
