Re: Broken hint bits (freeze)

From: Vladimir Borodin <root(at)simply(dot)name>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Dmitriy Sarafannikov <dsarafannikov(at)yandex(dot)ru>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Sergey Burladyan <eshkinkot(at)gmail(dot)com>
Subject: Re: Broken hint bits (freeze)
Date: 2017-06-07 07:12:30
Message-ID: 6178ED21-890F-4E6E-9035-10DABDCA5060@simply.name
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> 6 июня 2017 г., в 23:30, Sergey Burladyan <eshkinkot(at)gmail(dot)com> написал(а):
>
> Dmitriy Sarafannikov <dsarafannikov(at)yandex(dot)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…
https://simply.name

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2017-06-07 07:27:39 Re: PG10 transition tables, wCTEs and multiple operations on the same table
Previous Message Ashutosh Bapat 2017-06-07 06:28:58 Re: Adding support for Default partition in partitioning