Re: pgsql: pg_dump: scope indAttNames per index in getIndexes()

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Alexander Korotkov <akorotkov(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: pg_dump: scope indAttNames per index in getIndexes()
Date: 2026-06-05 05:47:51
Message-ID: CAPpHfdvds+5TXTkdcnntY8c6E5afCGq7EsuWu2KCP4dY5MaUtw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Hi, Michael!

On Fri, Jun 5, 2026 at 1:54 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Wed, Jun 03, 2026 at 10:01:44AM +0000, Alexander Korotkov wrote:
> > pg_dump: scope indAttNames per index in getIndexes()
> >
> > Author: Maksim Melnikov <m(dot)melnikov(at)postgrespro(dot)ru>
> > Reviewed-by: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
> > Discussion: https://postgr.es/m/be5fc489-587e-421f-bbb8-adb43cfd50f4@postgrespro.ru
> > Backpatch-through: 17
>
> Regarding this commit, we have as of today:
> $ git branch --contains 94c02de89c26
> + REL_18_STABLE
> $ git branch --contains 298bdd379552
> + master
>
> And there is nothing on REL_17_STABLE. Am I missing something or
> isn't this just a typo in the Backpatch-through tag?

Thank you for pointing. I've rechecked. The code that this commit is
intended to fix is introduced by 40e27d04b4f6, which appears first in
PG18. So, yes, it's a typo in the backpatch tag. Sorry for that.

------
Regards,
Alexander Korotkov
Supabase

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2026-06-05 07:08:51 pgsql: Handle element label and label property objects in object addres
Previous Message Michael Paquier 2026-06-05 05:30:24 pgsql: xml2: Fix stylesheet document leak in xslt_process()