Re: Doc chapter for Hash Indexes

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Doc chapter for Hash Indexes
Date: 2021-06-24 19:59:35
Message-ID: 20210624195935.GC16214@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

aOn Wed, Jun 23, 2021 at 12:56:51PM +0100, Simon Riggs wrote:
> On Wed, Jun 23, 2021 at 5:12 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> >
> > On Tue, Jun 22, 2021 at 2:31 PM Simon Riggs
> > <simon(dot)riggs(at)enterprisedb(dot)com> wrote:
> > >
> > > I attach both clean and compare versions.
> > >
> >
> > Do we want to hold this work for PG15 or commit in PG14 and backpatch
> > it till v10 where we have made hash indexes crash-safe? I would vote
> > for committing in PG14 and backpatch it till v10, however, I am fine
> > if we want to commit just to PG14 or PG15.
>
> Backpatch makes sense to me, but since not everyone will be reading
> this thread, I would look towards PG15 only first. We may yet pick up
> additional corrections or additions before a backpatch, if that is
> agreed.

Yeah, I think backpatching makes sense.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

If only the physical world exists, free will is an illusion.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2021-06-24 21:54:51 pgsql: Fix pattern matching logic for logs in TAP tests of pgbench
Previous Message vignesh C 2021-06-24 18:25:02 Re: Added schema level support for publication.