From: Sergey Burladyan <eshkinkot@gmail.com>
To: Vladimir Borodin <root@simply.name>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>,
  Dmitriy Sarafannikov <dsarafannikov@yandex.ru>,
  Amit Kapila <amit.kapila16@gmail.com>, Bruce Momjian <bruce@momjian.us>
Subject: Re: Broken hint bits (freeze)
References: <DA18C5E1-A115-4C1C-9F7C-E7B9A5F3EBC5@yandex.ru>
	<CAA4eK1L2n8stKZvOp3yrOCZJi4Z5eDuzmvhdPdbZUAc9qacRPg@mail.gmail.com>
	<2E86EB5F-50ED-4DE2-B14E-98EF8F62B2F2@simply.name>
	<CAA4eK1KtEDAKbq_40hSYBTgvTf88Jio4Q_DxiEK0dkjjXdg4_g@mail.gmail.com>
	<4C1127FC-74AE-4544-9B22-6A32FD0C0607@yandex.ru>
	<87wp8o506b.fsf@seb.koffice.internal>
	<6178ED21-890F-4E6E-9035-10DABDCA5060@simply.name>
Date: Wed, 07 Jun 2017 14:29:55 +0300
In-Reply-To: <6178ED21-890F-4E6E-9035-10DABDCA5060@simply.name> (Vladimir
	Borodin's message of "Wed, 7 Jun 2017 10:12:30 +0300")
Message-ID: <87fufc3uj0.fsf@seb.koffice.internal>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Vladimir Borodin <root@simply.name> writes:

> > 6 =D0=B8=D1=8E=D0=BD=D1=8F 2017 =D0=B3., =D0=B2 23:30, Sergey Burladyan=
 <eshkinkot@gmail.com> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
> >=20
> > Dmitriy Sarafannikov <dsarafannikov@yandex.ru> writes:
> >=20
> >> Starting and stopping master after running pg_upgrade but before rsync=
 to collect statistics
> >> was a bad idea.
> >=20
> > But, starting and stopping master after running pg_upgrade is *required*
> > by documentation:
> > https://www.postgresql.org/docs/9.6/static/pgupgrade.html
> >> f. Start and stop the new master cluster
> >> In the new master cluster, change wal_level to replica in the postgres=
ql.conf file and then start and stop the cluster.
> >=20
> > and there is no any suggestion to disable autovacuum for it.

> Yep. This should probably be fixed in the documentation?

I think so. There is some problem in pg_upgrade documentation, nothing abou=
t:
1. preventing heap change by vacuum, analyze, something also when master
   restarted after pg_upgrade but before rsync
2. log-shipping only standby cannot shutdown at the same checkpoint with
   master

I try to start discuss about this: https://www.postgresql.org/message-id/87=
y3ta49zp.fsf%40seb.koffice.internal
but without luck :-)=20

PS: I CC'd Bruce here.

--=20
Sergey Burladyan


--=20
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers