pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: 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 14:20:24 -0500
Message-ID: <6000.1069356024@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.BSO.4.44.0311201311200.19584-100000@detroit.arbor.net>
References: <Pine.BSO.4.44.0311201311200.19584-100000@detroit.arbor.net>

Chester Kustarz <chester@arbor.net> writes:
> i have some tables which are insert only. i do not want to vacuum them
> because there are never any dead tuples in them and the vacuum grows the
> indexes.

Those claims cannot both be true.  In any case, plain vacuum cannot grow
the indexes --- only a VACUUM FULL that moves a significant number of
rows could cause index growth.

> 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.

			regards, tom lane



view thread (35+ messages)  latest in thread

Message-ID: <6000.1069356024@sss.pgh.pa.us>
Permalink:  ../6000.1069356024@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/6000.1069356024@sss.pgh.pa.us

 · 

reply

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: 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: <6000.1069356024@sss.pgh.pa.us>

* 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