pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Sergey Burladyan <eshkinkot@gmail.com>
To: Vladimir Borodin <root@simply.name>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: Dmitriy Sarafannikov <dsarafannikov@yandex.ru>
Cc: Amit Kapila <amit.kapila16@gmail.com>
Cc: Bruce Momjian <bruce@momjian.us>
Subject: Re: Broken hint bits (freeze)
Date: Wed, 07 Jun 2017 14:29:55 +0300
Message-ID: <87fufc3uj0.fsf@seb.koffice.internal> (raw)
In-Reply-To: <6178ED21-890F-4E6E-9035-10DABDCA5060@simply.name>
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>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

Vladimir Borodin <root@simply.name> writes:

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

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


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



view thread (64+ messages)  latest in thread

Message-ID: <87fufc3uj0.fsf@seb.koffice.internal>
Permalink:  ../87fufc3uj0.fsf@seb.koffice.internal/
Also on:    postgresql.org/message-id/87fufc3uj0.fsf@seb.koffice.internal

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: eshkinkot@gmail.com, root@simply.name, dsarafannikov@yandex.ru, amit.kapila16@gmail.com, bruce@momjian.us
  Subject: Re: Broken hint bits (freeze)
  In-Reply-To: <87fufc3uj0.fsf@seb.koffice.internal>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox