Re: Opportunistically pruning page before update

From: James Coleman <jtc331(at)gmail(dot)com>
To: Peter Smith <smithpb2250(at)gmail(dot)com>
Cc: Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Peter Geoghegan <pg(at)bowt(dot)ie>
Subject: Re: Opportunistically pruning page before update
Date: 2024-01-23 01:47:55
Message-ID: CAAaqYe8vE6MJnh-qT1GOumAyNFdh7G0qRkG5taOY9qdFFngfGw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 22, 2024 at 8:21 PM James Coleman <jtc331(at)gmail(dot)com> wrote:
>
> See rebased patch attached.

I just realized I left a change in during the rebase that wasn't necessary.

v4 attached.

Regards,
James Coleman

Attachment Content-Type Size
v4-0002-Opportunistically-prune-to-avoid-building-a-new-p.patch application/octet-stream 3.7 KB
v4-0001-Allow-getting-lock-before-calling-heap_page_prune.patch application/octet-stream 4.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2024-01-23 02:02:23 Re: WIP Incremental JSON Parser
Previous Message Peter Smith 2024-01-23 01:32:35 Re: Make documentation builds reproducible