Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Multicolumn Primary Key
- From: "Matthew T. O'Connor" <matthew(at)zeut(dot)net>
- To: Steve Crawford <scrawford(at)pinpointresearch(dot)com>
- Cc: "Thomas F.O'Connell" <tfo(at)sitening(dot)com>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-general(at)postgresql(dot)org
- Subject: Re: Multicolumn Primary Key
- Date: Tue, 31 Aug 2004 19:44:33 -0400
- Message-id: <41350D61(dot)2020005(at)zeut(dot)net>
Steve Crawford wrote:
On Tuesday 31 August 2004 3:49 pm, Matthew T. O'Connor wrote: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.
I thought having pg_autovacuum do that, but seemed like overkill, but perhaps a command line option wouldn't be a bad thing. However, you could also just as easily do a manual vacuum analyze whenever you like.
Matthew
- References:
- Multicolumn Primary Key
- From: Thomas F . O'Connell
- Re: Multicolumn Primary Key
- From: Thomas F . O'Connell
- Re: Multicolumn Primary Key
- From: Matthew T. O'Connor
- Re: Multicolumn Primary Key
- From: Steve Crawford
- Multicolumn Primary Key
- Prev by Date: Re: Multicolumn Primary Key
- Next by Date: Suppress output from psql?
- Previous by thread: Re: Multicolumn Primary Key
- Next by thread: Re: Microsoft Project and PostgreSQL?
- Indexes: