Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dNKIT-0004M3-D1 for pgsql-hackers@arkaria.postgresql.org; Tue, 20 Jun 2017 14:38:25 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dNKIS-0006W0-8p for pgsql-hackers@arkaria.postgresql.org; Tue, 20 Jun 2017 14:38:24 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dNKGt-0003lw-Rz for pgsql-hackers@postgresql.org; Tue, 20 Jun 2017 14:36:48 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dNKGq-0007HN-Hn for pgsql-hackers@postgresql.org; Tue, 20 Jun 2017 14:36:46 +0000 Received: from bruce by momjian.us with local (Exim 4.84_2) (envelope-from ) id 1dNKGp-0000d7-7N; Tue, 20 Jun 2017 10:36:43 -0400 Date: Tue, 20 Jun 2017 10:36:43 -0400 From: Bruce Momjian To: Sergey Burladyan Cc: PostgreSQL-development , Amit Kapila , Dmitriy Sarafannikov , Vladimir Borodin Subject: Re: Broken hint bits (freeze) Message-ID: <20170620143643.GA24975@momjian.us> References: <87mv98af8j.fsf@seb.koffice.internal> <20170616164641.GP11450@momjian.us> <87fuezalc3.fsf@seb.koffice.internal> <20170619222113.GF3180@momjian.us> <20170620025919.GA28277@momjian.us> <20170620033726.GB28277@momjian.us> <87h8zb6kbx.fsf@seb.koffice.internal> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87h8zb6kbx.fsf@seb.koffice.internal> User-Agent: Mutt/1.5.23 (2014-03-12) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On Tue, Jun 20, 2017 at 01:10:26PM +0300, Sergey Burladyan wrote: > Bruce Momjian writes: > > > Uh, as I understand it the rsync is going to copy the missing WAL file > > > from the new master to the standby, right, and I think pg_controldata > > > too, so it should be fine. Have you tested to see if it fails? > > It need old WAL files from old version for correct restore heap > files. New WAL files from new version does not have this information. > > > The point is that we are checking the "Latest checkpoint location" to > > make sure all the WAL was replayed. We are never going to start the > > old standby server. Rsync is going to copy the missing/changed files. > > Only if missing/changed files changed in size, because rsync run with > --size-only it does not copy changed files with same size. I am sorry but I am not understanding. Step 10.b says: 10.b Make sure the new standby data directories do not exist Make sure the new standby data directories do not exist or are empty. If initdb was run, delete the standby server data directories. so the _entire_ new data directory is empty before rsync is run, meaning that it is an exact copy of the new master. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers