Re: Broken hint bits (freeze)

From: Sergey Burladyan <eshkinkot(at)gmail(dot)com>
To: Vladimir Borodin <root(at)simply(dot)name>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Dmitriy Sarafannikov <dsarafannikov(at)yandex(dot)ru>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: Broken hint bits (freeze)
Date: 2017-06-07 11:29:55
Message-ID: 87fufc3uj0.fsf@seb.koffice.internal
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Vladimir Borodin <root(at)simply(dot)name> writes:

> > 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?

I think so. There is some problem in pg_upgrade documentation, nothing about:
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/87y3ta49zp.fsf%40seb.koffice.internal
but without luck :-)

PS: I CC'd Bruce here.

--
Sergey Burladyan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2017-06-07 11:47:21 A bug in mapping attributes in ATExecAttachPartition()
Previous Message Heikki Linnakangas 2017-06-07 11:27:37 Re: Server ignores contents of SASLInitialResponse