From: | "Claudio Lapidus" <clapidus(at)hotmail(dot)com> |
---|---|
To: | "Bruno Wolff III" <bruno(at)wolff(dot)to>, "Shridhar Daithankar" <shridhar_daithankar(at)persistent(dot)co(dot)in> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Buglist |
Date: | 2003-08-22 15:35:50 |
Message-ID: | BAY7-DAV46FlF8HGmCv0003814f@hotmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Bruno Wolff III wote:
> On Fri, Aug 22, 2003 at 12:17:41 +0530,
> Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> wrote:
> >
> > Idea of autovacuum is to reduce load on vacuum full. If you set
shared_buffers
> > higher and FSM properly for he update/delete load, autovacuum is
expected to
> > catch most of the dead tuples in shared cache only. If it is successful
in
> > doubling the frequency on vacuum full, that's a big win, isn't it?
>
> If you run a normal vacuum often enough, you shouldn't need to regularly
> run vacuum full.
Hmm, here we have a certain table, sort of FIFO, rows get inserted all the
time, lay there for a couple of hours and get deleted "the other end
around". We run normal vacuum almost constantly, but the table keeps
growing. We had to implement a 'vacuum full' once a week to keep it under
control.
cl.
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2003-08-22 15:43:19 | Re: Collation rules and multi-lingual databases |
Previous Message | Greg Stark | 2003-08-22 15:21:09 | Re: move to usenet? |
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2003-08-22 15:41:50 | Implementing FQA Indexes (in Italian) -- Help? |
Previous Message | Greg Stark | 2003-08-22 15:28:55 | Re: [SQL] "SELECT IN" Still Broken in 7.4b |