Re: ltree_gist indexes broken after pg_upgrade from 12 to 13

Tomas Vondra <tomas.vondra@enterprisedb.com>

From: Tomas Vondra <tomas.vondra@enterprisedb.com>

To: Alexander Korotkov <aekorotkov@gmail.com>

Cc: Nikita Glukhov <n.gluhov@postgrespro.ru>, Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Andres Freund <andres@anarazel.de>

Date: 2022-03-10T12:09:12Z

Lists: pgsql-hackers

On 3/10/22 08:09, Alexander Korotkov wrote:
> On Tue, Mar 8, 2022 at 2:05 AM Alexander Korotkov <aekorotkov@gmail.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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix default signature length for gist_ltree_ops
- bad202c615c9 13.7 landed
- 7d30f59da714 14.3 landed
- 7e74aafc4335 15.0 landed
Implement operator class parameters
- 911e70207703 13.0 cited