| From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
|---|---|
| To: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
| Cc: | "Thomas F(dot)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: | 2004-08-31 23:44:33 |
| Message-ID: | 41350D61.2020005@zeut.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron St-Pierre | 2004-09-01 00:18:14 | Re: Table UPDATE is too slow |
| Previous Message | Steve Crawford | 2004-08-31 23:41:24 | Re: Multicolumn Primary Key |