From: Bruno Wolff III <bruno@wolff.to>
To: Rob Nagler <nagler@bivio.biz>
Cc: pgsql-performance@postgresql.org
Subject: Re: reindex/vacuum locking/performance?
Date: Fri, 3 Oct 2003 16:59:39 -0500
Message-ID: <20031003215939.GA24446@wolff.to> (raw)
In-Reply-To: <16253.61013.56254.526139@jump.bivio.com>
References: <16253.56074.737161.470428@jump.bivio.com>
<954.1065214676@sss.pgh.pa.us>
<16253.61013.56254.526139@jump.bivio.com>
On Fri, Oct 03, 2003 at 15:47:01 -0600,
Rob Nagler <nagler@bivio.biz> wrote:
> > vacuum full does require exclusive lock, plain vacuum does not.
>
> I think I need full, because there are updates on the table. As I
> understand it, an update in pg is an insert/delete, so it needs
> to be garbage collected.
Plain vacuum will mark the space used by deleted tuples as reusable.
Most of the time this is good enough and you don't need to run vacuum full.
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: bruno@wolff.to, nagler@bivio.biz
Subject: Re: reindex/vacuum locking/performance?
In-Reply-To: <20031003215939.GA24446@wolff.to>
* 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