From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: hus.mhd@gmail.com
Subject: 64.4.2. Bottom-up Index Deletion
Date: Tue, 12 Jul 2022 16:00:10 +0000
Message-ID: <165764161026.666.13998783616221095418@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/14/btree-implementation.html
Description:
on this url 64.4.2. Bottom-up Index Deletion,
https://www.postgresql.org/docs/14/btree-implementation.html#BTREE-DELETION
Would be nice to add a note: old tuple versions in the index referencing the
same logical row cannot be deleted by bottom up index deletion process when
older transactions that might require the old state the row are still
running That is what the LP_DEAD bit is for I believe?
hopefully my understanding is correct.
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-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, hus.mhd@gmail.com
Subject: Re: 64.4.2. Bottom-up Index Deletion
In-Reply-To: <165764161026.666.13998783616221095418@wrigleys.postgresql.org>
* 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