| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | gregory(at)arenius(dot)com |
| Subject: | pg_upgrade "configdir" vs "datadir" |
| Date: | 2019-07-26 21:23:28 |
| Message-ID: | 156417620850.1184.14753980334386939913@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/11/pgupgrade.html
Description:
pg_upgrade seems to assume that the datadir and the configdir are the same
but on Debian/Ubuntu they are not the same by default (installing from the
postgres repository).
The current documentation:
-d configdir
--old-datadir=configdir
the old database cluster configuration directory; environment variable
PGDATAOLD
-D configdir
--new-datadir=configdir
the new database cluster configuration directory; environment variable
PGDATANEW
In order for this to work on Debian/Ubuntu you need to also pass some
options with the actual configuration directory. For example:
-o 'config_file=/etc/postgresql/9.6/main/postgresql.conf'
-O 'config_file=/etc/postgresql/10/main/postgresql.conf'
I think the documentation could use some clarification on this point.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-07-26 22:02:42 | Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented |
| Previous Message | Liudmila Mantrova | 2019-07-26 18:08:47 | suspicious wording in pg_rewind docs |