Re: db growing out of proportion

From: Tomas Szepe <szepe(at)pinerecords(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: db growing out of proportion
Date: 2003-06-13 05:34:59
Message-ID: 20030613053459.GB23789@louise.pinerecords.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-performance

> [szepe(at)pinerecords(dot)com]
>
> > Peter Childs <blue(dot)dragon(at)blueyonder(dot)co(dot)uk> writes:
> > > On Fri, 30 May 2003, Tomas Szepe wrote:
> > >> Trouble is, as the rows in the tables get deleted/inserted/updated
> > >> (the frequency being a couple thousand rows per minute), the database
> > >> is growing out of proportion in size.
> >
> > > Would more regular vacuum help. I think a vaccum every hour may do
> > > the job.
> >
> > Also note that no amount of vacuuming will save you if the FSM is not
> > large enough to keep track of all the free space. The default FSM
> > settings, like all the other default settings in Postgres, are set up
> > for a small installation. You'd probably need to raise them by at least
> > a factor of 10 for this installation.
>
> Thanks, I'll try to tweak those settings and will let the list know how
> things went.

Well, raising max_fsm_pages to 500000 seems to have solved the problem
entirely. My thanks go to everyone who've offered their help.

--
Tomas Szepe <szepe(at)pinerecords(dot)com>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Serge Obeuf 2003-06-13 08:20:42 Re: pg_dumpall not working in batch
Previous Message Robert Creager 2003-06-13 03:49:34 Adjusting fsm values was Re: [BUGS] db growing out of proportion

Browse pgsql-performance by date

  From Date Subject
Next Message Vincent van Leeuwen 2003-06-13 12:39:22 Re: tweaking costs to favor nestloop
Previous Message Robert Creager 2003-06-13 03:49:34 Adjusting fsm values was Re: [BUGS] db growing out of proportion