Horton
Menu

Thread

  1. docs: Include database collation check on SQL from alter_collation.sgml

    Matheus Alcantara <matheusssilv97@gmail.com> — 2026-04-09T18:00:34Z

    Hi,

The ALTER COLLATION documentation section include a SQL that can be used
to identity all collations in the current database that need to be
refreshed due to a collation version miss match and the objects that
depend on them. However if there is objects that use the database
collation these objects are not returned by the query.

The attached patch change the query to include the database collation
check to report collation version miss match for objects that use the
database default collation as they are not stored on pg_depend.

--
Matheus Alcantara
EDB: https://www.enterprisedb.com

  2. Re: docs: Include database collation check on SQL from alter_collation.sgml

    Matheus Alcantara <matheusssilv97@gmail.com> — 2026-04-13T21:08:40Z

    On Thu Apr 9, 2026 at 3:00 PM -03, Matheus Alcantara wrote:
> Hi,
>
> The ALTER COLLATION documentation section include a SQL that can be used
> to identity all collations in the current database that need to be
> refreshed due to a collation version miss match and the objects that
> depend on them. However if there is objects that use the database
> collation these objects are not returned by the query.
>
> The attached patch change the query to include the database collation
> check to report collation version miss match for objects that use the
> database default collation as they are not stored on pg_depend.
>

The proposed SQL on the v1 patch still don't handle the cases where an
index is using the database default collation. 

The new v2 attached handle it properly. The new query is based on the
query suggested on Locale data changes wiki page [1] but with some
changes to check the collation version mismatch.


[1] https://wiki.postgresql.org/wiki/Locale_data_changes

--
Matheus Alcantara
EDB: https://www.enterprisedb.com