Re: [HACKERS] Broken hint bits (freeze) - Mailing list pgsql-hackers

From Vladimir Borodin
Subject Re: [HACKERS] Broken hint bits (freeze)
Date
Msg-id 6178ED21-890F-4E6E-9035-10DABDCA5060@simply.name
Whole thread Raw
In response to Re: [HACKERS] Broken hint bits (freeze)  (Sergey Burladyan <eshkinkot@gmail.com>)
Responses Re: [HACKERS] Broken hint bits (freeze)
List pgsql-hackers

6 июня 2017 г., в 23:30, Sergey Burladyan <eshkinkot@gmail.com> написал(а):

Dmitriy Sarafannikov <dsarafannikov@yandex.ru> writes:

Starting and stopping master after running pg_upgrade but before rsync to collect statistics
was a bad idea.

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 postgresql.conf file and then start and stop the cluster.

and there is no any suggestion to disable autovacuum for it.


Yep. This should probably be fixed in the documentation?


--
May the force be with you…

pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: [HACKERS] Adding support for Default partition in partitioning
Next
From: Thomas Munro
Date:
Subject: Re: [HACKERS] PG10 transition tables, wCTEs and multiple operationson the same table