Re: ltree_gist indexes broken after pg_upgrade from 12 to 13

From: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
To: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Cc: Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: ltree_gist indexes broken after pg_upgrade from 12 to 13
Date: 2022-03-10 12:09:12
Message-ID: 9f1043f6-08c1-56f3-0652-f6f59a7eda6f@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3/10/22 08:09, Alexander Korotkov wrote:
> On Tue, Mar 8, 2022 at 2:05 AM Alexander Korotkov <aekorotkov(at)gmail(dot)com> wrote:
>> ...
>>
>> Good. The revised patch is attached. Instead of adding argument to
>> LTREE_GET_ASIGLEN(), it introduces separate LTREE_GET_SIGLEN() and
>> LTREE_GET_ASIGLEN() macros.
>
> No feedback yet. I'm going to push this if no objections.
>

WFM. I certainly don't have a better idea how to fix this.

regards

--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Banck 2022-03-10 13:43:32 Re: PATCH: add "--config-file=" option to pg_rewind
Previous Message Amit Kapila 2022-03-10 12:02:42 Re: Skipping logical replication transactions on subscriber side