From: Heikki Linnakangas <heikki@enterprisedb.com>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: pgsql-patches <pgsql-patches@postgresql.org>
Subject: Re: Relation forks & FSM rewrite patches
Date: Fri, 04 Jul 2008 22:32:06 +0300
Message-ID: <486E7AB6.40804@enterprisedb.com> (raw)
In-Reply-To: <20080704163643.GB3893@alvh.no-ip.org>
References: <48651722.8020600@enterprisedb.com>
<1215161814.4051.36.camel@ebony.site>
<486DED1B.4020202@enterprisedb.com>
<1215169844.4051.95.camel@ebony.site>
<486E159D.2050405@enterprisedb.com>
<20080704163643.GB3893@alvh.no-ip.org>
Alvaro Herrera wrote:
> I wonder if we could instead make vacuum write a new FSM tree from
> scratch, rather than updating it piecemeal.
I'd like to move away from that, as we'll hopefully get some sort of
partial vacuum capability soon.
We might want to have some sort of bulk update operation, though, so
that you could refresh FSM information for say 100 pages, or one FSM
page, at a time. That would reduce the WAL traffic of a VACUUM
significantly, though I'm not sure how significant that is to begin with.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
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-patches@postgresql.org
Cc: heikki@enterprisedb.com, alvherre@commandprompt.com, simon@2ndquadrant.com
Subject: Re: Relation forks & FSM rewrite patches
In-Reply-To: <486E7AB6.40804@enterprisedb.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