Horton
Menu

Re: ltree_gist indexes broken after pg_upgrade from 12 to 13

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Korotkov <aekorotkov@gmail.com>
Cc: Tomas Vondra <tomas.vondra@enterprisedb.com>, Nikita Glukhov <n.gluhov@postgrespro.ru>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Andres Freund <andres@anarazel.de>
Date: 2022-03-10T22:36:50Z
Lists: pgsql-hackers 
Alexander Korotkov <aekorotkov@gmail.com> writes:
> Sorry for publishing a patch, which doesn't even compile.
> The attached version should be good.

OK, better.

So to clarify: we are going to back-patch as far as v13, and
then in the minor releases we are going to tell people they
need to REINDEX all gist indexes on ltree?  If so, please
make that clear in the commit message, so I don't forget it
come May ;-)

Also, it looks like reindex is *not* required for indexes on
ltree[] ?  That is, gist_ltree_ops indexes are affected but
not gist__ltree_ops?

			regards, tom lane

Commits

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

  1. Fix default signature length for gist_ltree_ops

  2. Implement operator class parameters