| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | hus(dot)mhd(at)gmail(dot)com |
| Subject: | 64.4.2. Bottom-up Index Deletion |
| Date: | 2022-07-12 16:00:10 |
| Message-ID: | 165764161026.666.13998783616221095418@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2022-07-12 18:46:14 | Re: No documentation exists about ecpg ORACLE comptaible mode |
| Previous Message | Tom Lane | 2022-07-12 13:50:27 | Re: Docs for string_to_array missing for Postgres 14 |