MIME-Version: 1.0
From: Don Seiler <don@seiler.us>
Date: Thu, 7 Dec 2017 11:28:12 -0600
Message-ID: 
 <CAHJZqBD0u9dCERpYzK6BkRv=663AmH==DFJpVC=M4Xg_rq2=CQ@mail.gmail.com>
Subject: Bug in pg_upgrade standby rsync doc
To: pgsql-docs@lists.postgresql.org
Content-Type: multipart/alternative; boundary="089e0822e438b4fd13055fc36568"
Precedence: bulk

--089e0822e438b4fd13055fc36568
Content-Type: text/plain; charset="UTF-8"

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

--089e0822e438b4fd13055fc36568
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">In step 10 of the pg_upgrade doc at=C2=A0<a href=3D"https:=
//www.postgresql.org/docs/9.6/static/pgupgrade.html">https://www.postgresql=
.org/docs/9.6/static/pgupgrade.html</a>, it uses this example for rsyncing =
the main $PGDATA dir to the standby:<br clear=3D"all"><div><br></div><div><=
pre class=3D"gmail-PROGRAMLISTING" style=3D"font-size:1.3em;color:rgb(0,0,0=
);border-width:1px;border-style:solid;padding:2ex;margin-top:2ex;margin-bot=
tom:2ex;margin-left:2ex;overflow:auto;border-radius:8px;border-color:rgb(20=
7,207,207);background-color:rgb(247,247,247)">rsync --archive --delete --ha=
rd-links --size-only --no-inc-recursive /opt/PostgreSQL/9.5/data \
      /opt/PostgreSQL/9.6/data standby.example.com:/opt/PostgreSQL</pre></d=
iv><div><br></div><div>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/l=
ib/pgsql/data appeared to be the old 9.2 contents.</div><div><br></div><div=
>I suspect this is because the &quot;data&quot; 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.</div>=
<div><br></div><div>When I run the command with the &quot;data&quot; dir, s=
o that I&#39;m just specifying 9.2 and 9.6, it works as desired. eg:</div><=
div><br></div><div><pre class=3D"gmail-PROGRAMLISTING" style=3D"font-size:1=
.3em;color:rgb(0,0,0);border-width:1px;border-style:solid;padding:2ex;margi=
n-top:2ex;margin-bottom:2ex;margin-left:2ex;overflow:auto;border-radius:8px=
;border-color:rgb(207,207,207);background-color:rgb(247,247,247)">rsync --a=
rchive --delete --hard-links --size-only --no-inc-recursive /opt/PostgreSQL=
/9.5 \
      /opt/PostgreSQL/9.6 standby.example.com:/opt/PostgreSQL</pre></div><d=
iv><br></div><div>FWIW I was upgrading from 9.2.22 to 9.6.6 on CentOS 6.</d=
iv><div><br></div>-- <br><div class=3D"gmail_signature"><div dir=3D"ltr"><d=
iv>Don Seiler<br><a href=3D"http://www.seiler.us" target=3D"_blank">www.sei=
ler.us</a></div></div></div>
</div>

--089e0822e438b4fd13055fc36568--