diff options
| author | Peter Eisentraut <peter@eisentraut.org> | 2022-02-14 08:09:04 +0100 |
|---|---|---|
| committer | Peter Eisentraut <peter@eisentraut.org> | 2022-02-14 08:27:26 +0100 |
| commit | 37851a8b83d3d57ca48736093b10aa5f3bc0c177 (patch) | |
| tree | 5da6f597063d9579937e80aaf66d92c50ef73029 /src/tutorial/syscat.source | |
| parent | 9898c5e03c40c133a9a01d8b2b36cb7c990b30d5 (diff) | |
| download | postgresql-37851a8b83d3d57ca48736093b10aa5f3bc0c177.tar.gz postgresql-37851a8b83d3d57ca48736093b10aa5f3bc0c177.zip | |
Database-level collation version tracking
This adds to database objects the same version tracking that collation
objects have. There is a new pg_database column datcollversion that
stores the version, a new function
pg_database_collation_actual_version() to get the version from the
operating system, and a new subcommand ALTER DATABASE ... REFRESH
COLLATION VERSION.
This was not originally added together with pg_collation.collversion,
since originally version tracking was only supported for ICU, and ICU
on a database-level is not currently supported. But we now have
version tracking for glibc (since PG13), FreeBSD (since PG14), and
Windows (since PG13), so this is useful to have now.
Reviewed-by: Julien Rouhaud <rjuju123@gmail.com>
Discussion: https://www.postgresql.org/message-id/flat/f0ff3190-29a3-5b39-a179-fa32eee57db6%40enterprisedb.com
Diffstat (limited to 'src/tutorial/syscat.source')
0 files changed, 0 insertions, 0 deletions