Peter Eisentraut f85a485f89 Add support for automatically updating Unicode derived files
We currently have several sets of files generated from data provided
by Unicode.  These all have ad hoc rules and instructions for updating
when new Unicode versions appear, and it's not done consistently.

This patch centralizes and automates the process and makes it part of
the release checklist.  The Unicode and CLDR versions are specified in
Makefile.global.in.  There is a new make target "update-unicode" that
downloads all the relevant files and runs the generation script.

There is also a new script for generating the table of combining
characters for ucs_wcwidth().  That table is now in a separate include
file rather than hardcoded into the middle of other code.  This is
based on the script that was used for generating
d8594d123c155aeecd47fc2450f62f5100b2fbf0, but the script itself wasn't
committed at that time.

Reviewed-by: John Naylor <john.naylor@2ndquadrant.com>
Discussion: https://www.postgresql.org/message-id/flat/c8d05f42-443e-6c23-819b-05b31759a37c@2ndquadrant.com
2020-01-09 10:08:14 +01:00
..
2020-01-01 12:21:45 -05:00
2020-01-01 12:21:45 -05:00
2020-01-01 12:21:45 -05:00
2020-01-01 12:21:45 -05:00
2020-01-01 12:21:45 -05:00
2019-06-03 13:44:03 +09:00
2020-01-01 12:21:45 -05:00
2020-01-01 12:21:45 -05:00
2020-01-01 12:21:45 -05:00
2020-01-01 12:21:45 -05:00
2020-01-01 12:21:45 -05:00
2020-01-01 12:21:45 -05:00
2020-01-01 12:21:45 -05:00
2017-09-14 22:22:59 -04:00
2019-11-28 16:48:37 -03:00
2020-01-01 12:21:45 -05:00
2020-01-01 12:21:45 -05:00
2020-01-01 12:21:45 -05:00
2019-11-28 16:48:37 -03:00
2020-01-01 12:21:45 -05:00
2020-01-01 12:21:45 -05:00
2020-01-01 12:21:45 -05:00
2020-01-01 12:21:45 -05:00
2019-11-28 16:48:37 -03:00
2020-01-01 12:21:45 -05:00
2020-01-01 12:21:45 -05:00
2020-01-01 12:21:45 -05:00
2020-01-01 12:21:45 -05:00
2020-01-01 12:21:45 -05:00
2020-01-01 12:21:45 -05:00
2018-04-03 09:47:18 -04:00

The PostgreSQL contrib tree
---------------------------

This subtree contains porting tools, analysis utilities, and plug-in
features that are not part of the core PostgreSQL system, mainly
because they address a limited audience or are too experimental to be
part of the main source tree.  This does not preclude their
usefulness.

User documentation for each module appears in the main SGML
documentation.

When building from the source distribution, these modules are not
built automatically, unless you build the "world" target.  You can
also build and install them all by running "make all" and "make
install" in this directory; or to build and install just one selected
module, do the same in that module's subdirectory.

Some directories supply new user-defined functions, operators, or
types.  To make use of one of these modules, after you have installed
the code you need to register the new SQL objects in the database
system by executing a CREATE EXTENSION command.  In a fresh database,
you can simply do

    CREATE EXTENSION module_name;

See the PostgreSQL documentation for more information about this
procedure.