Re: pgsql: pg_dump: scope indAttNames per index in getIndexes()
Re: pgsql: pg_dump: scope indAttNames per index in getIndexes()
Hi Alexander, On Wed, Jun 03, 2026 at 10:01:44AM +0000, Alexander Korotkov wrote: > pg_dump: scope indAttNames per index in getIndexes() > > Author: Maksim Melnikov > Reviewed-by: Alexander Korotkov > 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? -- Michael
Re: pgsql: pg_dump: scope indAttNames per index in getIndexes()
От:
Alexander Korotkov <aekorotkov@gmail.com>
Дата:
Hi, Michael! On Fri, Jun 5, 2026 at 1:54 AM Michael Paquier 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 > > Reviewed-by: Alexander Korotkov > > 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