From: Ron Mayer <rm_pg@cheapcomplexdevices.com>
To: Heikki Linnakangas <heikki@enterprisedb.com>
Subject: Re: Non-blocking vacuum full
Date: Fri, 28 Sep 2007 19:46:28 -0700
Message-ID: <46FDBC84.2000205@cheapcomplexdevices.com> (raw)
In-Reply-To: <46FD5695.6000302@enterprisedb.com>
References: <20070928180649.GA6579@hyperion.scode.org>
<46FD5695.6000302@enterprisedb.com>
Heikki Linnakangas wrote:
> Peter Schuller wrote:
>> to have a slow background process (similar to normal non-full vacuums
> ...
> I think it's doable, if you take a copy of the tuple, and set the ctid
> pointer on the old one like an UPDATE, and wait until the old tuple is
> no longer visible to anyone before removing it. It does require some
> changes to tuple visibility code.
Wouldn't just having this slow background process
repeatedly alternating between
update table set anycol=anycol where ctid > [some ctid near the end]
and running normal VACUUM statements do what the original poster
was asking? And with 8.3, I guess also avoiding HOT?
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: rm_pg@cheapcomplexdevices.com, heikki@enterprisedb.com
Subject: Re: Non-blocking vacuum full
In-Reply-To: <46FDBC84.2000205@cheapcomplexdevices.com>
* 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