From: Nathan Bossart <nathandbossart@gmail.com>
To: Christophe Pettus <xof@thebuild.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Documentation bug at: current/sql-vacuum.html, Notes
Date: Wed, 26 Jul 2023 10:55:50 -0700
Message-ID: <20230726175550.GA3310393@nathanxps13> (raw)
In-Reply-To: <292046F0-7FA9-4AAE-A632-79EAD3D1280F@thebuild.com>
References: <292046F0-7FA9-4AAE-A632-79EAD3D1280F@thebuild.com>
On Wed, Jul 26, 2023 at 10:39:41AM -0700, Christophe Pettus wrote:
> Isn't this backwards?
>
>> If index cleanup is not performed regularly, performance may suffer, because as the table is modified indexes will accumulate dead tuples and the table itself will accumulate dead line pointers that cannot be removed until index cleanup is completed.
>
> Indexes have line pointers, tables have tuples, so it should read:
>
>> If index cleanup is not performed regularly, performance may suffer, because as the table is modified indexes will accumulate dead line pointers and the table itself will accumulate dead tuples that cannot be removed until index cleanup is completed.
I believe the current phrasing is correct. VACUUM will be able to reclaim
the tuple space in the heap, but the line pointers must remain until their
corresponding index tuples are removed.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.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-bugs@postgresql.org
Cc: nathandbossart@gmail.com, xof@thebuild.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Documentation bug at: current/sql-vacuum.html, Notes
In-Reply-To: <20230726175550.GA3310393@nathanxps13>
* 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