From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@dcc.uchile.cl>
Cc: Tambet Matiisen <t.matiisen@aprote.ee>
Cc: josh@agliodbs.com, Bill Chandler <billybobc1210@yahoo.com>
Cc: pgsql-perform <pgsql-performance@postgresql.org>
Subject: Re: Question on REINDEX
Date: Tue, 19 Apr 2005 14:34:35 -0400
Message-ID: <23413.1113935675@sss.pgh.pa.us> (raw)
In-Reply-To: <20050419182826.GA18949@dcc.uchile.cl>
References: <A66A11DBF5525341AEF6B8DE39CDE77008806E@black.aprote.com>
<21097.1113919600@sss.pgh.pa.us>
<20050419182826.GA18949@dcc.uchile.cl>
Alvaro Herrera <alvherre@dcc.uchile.cl> writes:
> Am I right in thinking that vacuum does at least two passes: one
> front-to-back to find removable tuples, and other back-to-front for
> movement?
VACUUM FULL, yes. VACUUM only does the first one.
> I know maintenance_work_mem is used for storing TIDs of to-be-moved
> tuples for index cleanup ... how does it relate to the above?
TIDs of to-be-deleted tuples, actually. Movable tuples aren't stored,
they're just found on-the-fly during the back-to-front pass.
regards, tom lane
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, alvherre@dcc.uchile.cl, t.matiisen@aprote.ee, billybobc1210@yahoo.com
Subject: Re: Question on REINDEX
In-Reply-To: <23413.1113935675@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