From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
---|---|
To: | Christophe Pettus <xof(at)thebuild(dot)com> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Documentation bug at: current/sql-vacuum.html, Notes |
Date: | 2023-07-26 17:55:50 |
Message-ID: | 20230726175550.GA3310393@nathanxps13 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Christophe Pettus | 2023-07-26 18:12:42 | Re: Documentation bug at: current/sql-vacuum.html, Notes |
Previous Message | Christophe Pettus | 2023-07-26 17:39:41 | Documentation bug at: current/sql-vacuum.html, Notes |