v.25.5Experimental Feature

Indexes of type full_text were renamed

Indexes of type full_text were renamed to gin. This follows the more familiar terminology of PostgreSQL and other databases. Existing indexes of type full_text remain loadable but they will throw an exception (suggesting gin indexes instead) when one tries to use them in searches. #79024 (Robert Schulze).
Indexes of type full_text have been renamed to gin to align with the terminology used in PostgreSQL and other databases.

Why it matters

This change improves consistency and familiarity for users by adopting the widely known gin nomenclature for full-text indexes. It helps avoid confusion and makes the indexing approach more intuitive. Existing full_text indexes remain loadable but will throw an exception when used in searches, guiding users to switch to the new gin index type.

How to use it

When creating indexes for full-text search, use gin as the index type instead of full_text. Existing full_text indexes should be migrated or recreated as gin indexes to avoid exceptions during searches.