From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Chester Kustarz <chester(at)arbor(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-performance(at)postgresql(dot)org, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] More detail on settings for pgavd? |
Date: | 2003-11-20 23:18:27 |
Message-ID: | 3FBD4BC3.8030003@zeut.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Tom Lane wrote:
>Chester Kustarz <chester(at)arbor(dot)net> writes:
>
>
>>vacuum is to reclaim dead tuples. this means it depends on update and
>>delete. analyze depends on data values/distribution. this means it depends on
>>insert, update, and delete. thus the dependencies are slightly different
>>between the 2 operations, an so you can come up with use-cases that
>>justify running either more frequently.
>>
>>
>Agreed.
>
>
And that is why pg_autovacuum looks at insert, update and delete when
deciding to do an analyze, but only looks at update and delete when
deciding to do a vacuum. In addition, this is why pg_autovacuum was
given knobs so that the vacuum and analyze thresholds can be set
independently.
Matthew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-11-21 00:07:41 | Re: logical column position |
Previous Message | Tom Lane | 2003-11-20 23:14:13 | Re: PANIC: rename from /data/pg_xlog/0000002200000009 |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-11-21 00:17:01 | Re: duration logging setting in 7.4 |
Previous Message | Tom Lane | 2003-11-20 22:58:40 | Re: Problem with insert into select... |