Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: Multicolumn Primary Key


  • From: Steve Crawford <scrawford(at)pinpointresearch(dot)com>
  • To: "Matthew T. O'Connor" <matthew(at)zeut(dot)net>, "Thomas F.O'Connell" <tfo(at)sitening(dot)com>
  • Cc: Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-general(at)postgresql(dot)org
  • Subject: Re: Multicolumn Primary Key
  • Date: Tue, 31 Aug 2004 16:41:24 -0700
  • Message-id: <200408311641(dot)24089(dot)scrawford(at)pinpointresearch(dot)com>

On Tuesday 31 August 2004 3:49 pm, Matthew T. O'Connor wrote:
> Thomas F.O'Connell wrote:
> > On Aug 31, 2004, at 4:34 PM, Martijn van Oosterhout wrote:
> >> Otherwise, have you VACUUM ANALYZEd recently?
> >
> > Argh! That seems to have been it. I have pg_autovacuum running,
> > so it didn't occur to me.
>
> pg_autovacuum only knows about table activity that has taken place
> while it's running.  Example:  Table A has an analyze threshold of
> 1000, if you perform 999 updates on table A, then kill and restart
> pg_autovacuum, you will have to perform another 1000 updates before
> pg_autovacuum performs an ANALYZE.  This is a large limitation of
> the current implementation.
>
> I tried to fix this for 8.0, but my autovacuum improvements didn't
> make the cut.

As a quick-'n'-dirty "fix", what about a command-line option to 
autovacuum that tells it to vacuum analyze all tables on startup? At 
least it would start in a somewhat known condition.

Cheers,
Steve



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group