| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | carl(dot)witt(at)knime(dot)com |
| Subject: | ALTER DATABASE lacks documentation of REFRESH COLLATION VERSION |
| Date: | 2025-06-10 08:32:40 |
| Message-ID: | 174954436017.789.17527208973511012295@wrigleys.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/17/sql-alterdatabase.html
Description:
The documentation of ALTER DATABASE mentions four forms and then skips to
"The remaining forms change the session default for a run-time configuration
variable", omitting the documentation of the fifth form
```
ALTER DATABASE name REFRESH COLLATION VERSION
```
It would be useful to have more information on what that command does, which
permissions it requires, whether the database can be used during this
operation, etc.
This command is relatively important since after operating system updates,
collations will often mismatch, issuing an warning that asks the
administrator to run this command.
```WARNING: database "..." has a collation version mismatch
DETAIL: The database was created using collation version 2.35, but the
operating system provides version 2.39.
HINT: Rebuild all objects in this database that use the default collation
and run ALTER DATABASE stats REFRESH COLLATION VERSION, or build PostgreSQL
with the right library version.
```
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2025-06-10 11:30:43 | Query to identify all collations in the current database that need to be refreshed |
| Previous Message | Robert Treat | 2025-06-06 18:11:17 | Re: Add missing references to database object statistics manipulation functions in documentation |