Re: Default collation changes leave indexes in invalid state - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: Default collation changes leave indexes in invalid state
Date
Msg-id 20190911152229.GA24006@alvherre.pgsql
Whole thread Raw
In response to Re: Default collation changes leave indexes in invalid state  (Vincent Van Driessche <vincent@dabble.be>)
List pgsql-bugs
On 2019-Sep-11, Vincent Van Driessche wrote:

> If I understand it correctly you are saying: “If you run queries like this, you’d better know what you are doing”?
> Is there a more supported way to change the default collation on PostgreSQL?

I don't think there's a supported way to change the default collation on
an existing database.  You would have to dump and restore in order to
achieve that cleanly.  That would be my advice.

Part of the reason that there isn't a way to do this is that it isn't a
trivial change such as a single catalog update.  If you want to use this
hack, fine -- it's your database.  However, as you noticed, you will
also have to reindex many indexes (which? it's up to you to find out),
and there likely are other changes that you need to do.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-bugs by date:

Previous
From: Vincent Van Driessche
Date:
Subject: Re: Default collation changes leave indexes in invalid state
Next
From: Tom Lane
Date:
Subject: Re: BUG #15804: Assertion failure when using logging_collector with EXEC_BACKEND