[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [GENERAL] Multicolumn Primary Key
From:       "Matthew T. O'Connor" <matthew () zeut ! net>
Date:       2004-08-31 23:44:33
Message-ID: 41350D61.2020005 () zeut ! net
[Download RAW message or body]

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



---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match
[prev in list] [next in list] [prev in thread] [next in thread]