Re: Q: documentation improvement re collation version mismatch

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Q: documentation improvement re collation version mismatch
Date: 2022-11-10 14:39:03
Message-ID: 3515c6ba-0487-1ead-ef3d-84541767f370@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 11/10/22 08:33, Julien Rouhaud wrote:
> On Thu, Nov 10, 2022 at 08:04:37AM -0600, Ron wrote:
>> On 11/10/22 02:33, Julien Rouhaud wrote:
>> [snip]
>>> For now, the only safe way to go is either reindex everything, or everything
>>> except some safe cases (non-partial indexes on plain-non-collatable datatypes
>>> only). Usually, those safe cases are usually enough to avoid most of useless
>>> reindex activity.
>> In this situation, I queried for all indices with text-type columns
>> (including UUID) and reindexed them.
> That may work in your personal use case, but it's not generally safe. I hope
> you don't have partial indexes,

Aren't partial indices listed in pg_indexes?

> expressions or functions that internally relied
> on collatable datatypes,

No such indices.

> or indexes on other plain collatable datatypes.

What other data types besides the text types are collatable?

--
Angular momentum makes the world go 'round.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Julien Rouhaud 2022-11-10 14:50:39 Re: Q: documentation improvement re collation version mismatch
Previous Message Julien Rouhaud 2022-11-10 14:33:29 Re: Q: documentation improvement re collation version mismatch