From: | Don Seiler <don(at)seiler(dot)us> |
---|---|
To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Bug in pg_upgrade standby rsync doc |
Date: | 2017-12-07 17:28:12 |
Message-ID: | CAHJZqBD0u9dCERpYzK6BkRv=663AmH==DFJpVC=M4Xg_rq2=CQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
In step 10 of the pg_upgrade doc at
https://www.postgresql.org/docs/9.6/static/pgupgrade.html, it uses this
example for rsyncing the main $PGDATA dir to the standby:
rsync --archive --delete --hard-links --size-only --no-inc-recursive
/opt/PostgreSQL/9.5/data \
/opt/PostgreSQL/9.6/data standby.example.com:/opt/PostgreSQL
However when I ran this (substituting /var/lib/pgsql for /opt/PostgreSQL),
I found that it put a directory under /var/lib/pgsql/data, and my 9.6/data
dir was still empty. Furthermore, what was in /var/lib/pgsql/data appeared
to be the old 9.2 contents.
I suspect this is because the "data" directories are two levels below the
parent directory specified at the end of the command. When I used the
similar command for separate tablespaces, it worked as expected.
When I run the command with the "data" dir, so that I'm just specifying 9.2
and 9.6, it works as desired. eg:
rsync --archive --delete --hard-links --size-only --no-inc-recursive
/opt/PostgreSQL/9.5 \
/opt/PostgreSQL/9.6 standby.example.com:/opt/PostgreSQL
FWIW I was upgrading from 9.2.22 to 9.6.6 on CentOS 6.
--
Don Seiler
www.seiler.us
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Finnerty | 2017-12-12 03:56:04 | Re: Why the planner does not use index for a large amount of data? |
Previous Message | madhevan | 2017-12-07 17:20:59 | listen/notify sequence not working in windows10 pgAdmin 4 |