On Wed, Nov 9, 2022 at 4:06 PM David G. Johnston
wrote:
> Ok, so the "most recent live tuple" - this in an update, there has to be one.
> Can that live tuple that is being updated ever be removed by this process?
No.
> I'm not sure what the long-running transaction has to do with this though -
On Wed, Nov 9, 2022 at 4:29 PM Peter Geoghegan wrote:
> On Wed, Nov 9, 2022 at 2:20 PM David G. Johnston
> wrote:
> > Maybe a bit more explicitness is in order.
>
> Yeah, maybe.
>
> > On the point of "will generally need to coexist" - I don't see why we
> are being wishy-washy here, though.
>
>
On Wed, Nov 9, 2022 at 2:20 PM David G. Johnston
wrote:
> Maybe a bit more explicitness is in order.
Yeah, maybe.
> On the point of "will generally need to coexist" - I don't see why we are
> being wishy-washy here, though.
Because sometimes it will take a relatively long time (say in the
pres
On Mon, Nov 7, 2022 at 5:20 PM Peter Geoghegan wrote:
> Hi Hussein,
>
> Apologies for the very delayed response. I'm aware that you've taken
> an interest in this subject as part of your YouTube channel. Thanks
> for publicizing the work!
>
> On Tue, Jul 12, 2022 at 7:14 PM PG Doc comments form
>
Hi Hussein,
Apologies for the very delayed response. I'm aware that you've taken
an interest in this subject as part of your YouTube channel. Thanks
for publicizing the work!
On Tue, Jul 12, 2022 at 7:14 PM PG Doc comments form
wrote:
> Would be nice to add a note: old tuple versions in the inde
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
