Re: Postgresql Automatic vacuum

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Christoph Dalitz <christoph(dot)dalitz(at)hs-niederrhein(dot)de>
Cc: shridhar_daithankar(at)persistent(dot)co(dot)in, pgsql-general(at)postgresql(dot)org
Subject: Re: Postgresql Automatic vacuum
Date: 2002-09-24 03:34:18
Message-ID: 20020924033418.GB16430@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Sep 23, 2002 at 08:14:58PM +0200, Christoph Dalitz wrote:
> >
> > I have written a small daemon that can automatically vacuum PostgreSQL
> > database, depending upon activity per table.
> >
> Sorry if this is an FAQ, but I have not found it in the docs:
>
> Why can't PostgreSQL collect the statistic information itself automatically?
> Are there any plans to implement this?
>
> PG is the only database I know that places the burdon to keep PG's internal
> statistics in the catalog up to date upon the database user.

I think it's history. For a long time the only way to update the statistics
was duraing a vacuum which locked the table. So it was unreasonable to do
that in the background. It is only recently the ANALYZE was seperated out.

Similarly, postgresql has no cron job system, that's what cron is for. The
statistics collector now running continuously is new so it is heading in the
right direction. If you can come up with some ideas as to when to trigger
automatically, feel free to contribute a patch. It may be accepted.

--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> There are 10 kinds of people in the world, those that can do binary
> arithmetic and those that can't.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2002-09-24 03:35:13 Re: [GENERAL] CURRENT_TIMESTAMP
Previous Message Bruce Momjian 2002-09-24 03:18:18 Re: [SQL] Monitoring a Query