Subject: Re: BUG #17220: ALTER INDEX ALTER COLUMN SET (..) with an optionless
 opclass makes index and table unusable
To: postgresql@zr40.nl, Alexander Korotkov <aekorotkov@gmail.com>
References: <17220-15d684c6c2171a83@postgresql.org>
Cc: pgsql-bugs@lists.postgresql.org
From: Vik Fearing <vik@postgresfriends.org>
Message-ID: <9b91d241-4d05-e5a4-67da-5b8acdb9a2f1@postgresfriends.org>
Date: Mon, 11 Oct 2021 20:03:13 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <17220-15d684c6c2171a83@postgresql.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/9b91d241-4d05-e5a4-67da-5b8acdb9a2f1%40postgresfriends.org>
Precedence: bulk

On 10/11/21 5:25 PM, PG Bug reporting form wrote:
> 
> User 'musttu' on IRC reported the following bug: After running "ALTER INDEX
> some_idx ALTER COLUMN expr SET (n_distinct=100)", the index and table become
> unusable. All further statements involving the table result in: "ERROR: 
> operator class text_ops has no options".
> 
> They reported this on the RDS version of 13.3, but I've been able to
> reproduce this on Debian with 13.4 and 14.0. It does not reproduce on 12.8,
> all statements succeed on that version.

This was broken by 911e702077 (Implement operator class parameters).
-- 
Vik Fearing