| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Greg Burd <greg(at)burd(dot)me> |
| Cc: | vignesh C <vignesh21(at)gmail(dot)com>, Hayato Kuroda <kuroda(dot)hayato(at)fujitsu(dot)com>, Joao Rito <joaovictor(dot)rito(at)gmail(dot)com>, shihao zhong <zhong950419(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Jeff Davis <pgsql(at)j-davis(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Hash index: stop registering pin-only bucket pages in WAL (remove REGBUF_NO_CHANGE) |
| Date: | 2026-11-18 07:13:01 |
| Message-ID: | CAA4eK1+TQjo9FzEvTfdGVKuQ=cRVRJP7vjuwObU+AyksQg=5=Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 18, 2026 at 1:51 AM Greg Burd <greg(at)burd(dot)me> wrote:
>
> Amit, Vignesh,
>
> Agreed, and thanks Vignesh for splitting it out. v13 is what I had in
> mind: the torn-page read fix on its own, backpatchable, with the
> recovery test and the HEAD-only rework (dropping the pin-only
> registration, removing REGBUF_NO_CHANGE) left for a separate commit on
> master once this is in.
>
Pushed. Next, I suggest we can work on the patch for "dropping the
pin-only registration". Once that is committed, we can move to
removing REGBUF_NO_CHANGE.
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2026-11-18 07:13:50 | Re: Assertion failure with temporary relations in single-user mode |
| Previous Message | Amit Langote | 2026-11-18 07:12:57 | Re: Two more RI fast-path issues |