| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | zhoushulin1992(at)gmail(dot)com |
| Subject: | 'pg_global' cannot be used as default_tablespace. |
| Date: | 2020-11-10 08:28:08 |
| Message-ID: | 160499688847.25495.8682880307938679648@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/bug-reporting.html
Description:
Tablespace 'pg_global' is one of the two auto-generated tablespace by
initdb, and 'pg_global' should not be used as the default_tablespace, since
it is used for shared system catalogs. However, none of these information is
recorded in the doc
https://www.postgresql.org/docs/11/runtime-config-client.html and
https://www.postgresql.org/docs/11/manage-ag-tablespaces.html. In case of
some mishandling to use 'pg_global' as a default_tablespace value, it is
better to record it in the doc of
https://www.postgresql.org/docs/11/manage-ag-tablespaces.html.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2020-11-10 08:29:48 | Tips about using mount point directly as the data_directory. |
| Previous Message | PG Doc comments form | 2020-11-10 08:25:27 | The relationship between 'min_wal_size', 'max_wal_size' and 'wal_segment_size' is not record. |