From: Matthew T. O'Connor <matthew@zeut.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Chester Kustarz <chester@arbor.net>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org, PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] More detail on settings for pgavd?
Date: Thu, 20 Nov 2003 18:18:27 -0500
Message-ID: <3FBD4BC3.8030003@zeut.net> (raw)
In-Reply-To: <6000.1069356024@sss.pgh.pa.us>
References: <Pine.BSO.4.44.0311201311200.19584-100000@detroit.arbor.net>
<6000.1069356024@sss.pgh.pa.us>
Tom Lane wrote:
>Chester Kustarz <chester@arbor.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: matthew@zeut.net, tgl@sss.pgh.pa.us, chester@arbor.net, josh@agliodbs.com, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] More detail on settings for pgavd?
In-Reply-To: <3FBD4BC3.8030003@zeut.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox