Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dLy9O-0002XY-4C for pgsql-hackers@arkaria.postgresql.org; Fri, 16 Jun 2017 20:47:26 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dLy9N-0000mi-Jy for pgsql-hackers@arkaria.postgresql.org; Fri, 16 Jun 2017 20:47:25 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dLy9M-0000la-E2 for pgsql-hackers@postgresql.org; Fri, 16 Jun 2017 20:47:24 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dLy9I-0003Lc-Pa for pgsql-hackers@postgresql.org; Fri, 16 Jun 2017 20:47:23 +0000 Received: from bruce by momjian.us with local (Exim 4.84_2) (envelope-from ) id 1dLy9G-000349-G1; Fri, 16 Jun 2017 16:47:18 -0400 Date: Fri, 16 Jun 2017 16:47:18 -0400 From: Bruce Momjian To: Sergey Burladyan Cc: Vladimir Borodin , Amit Kapila , Dmitriy Sarafannikov , pgsql-hackers Subject: Re: Broken hint bits (freeze) Message-ID: <20170616204718.GD5081@momjian.us> References: <948C9927-CC63-47F7-87B9-1FA5921E6D4A@yandex.ru> <0DFC2046-3025-465E-BBB8-1E55479A9B7D@simply.name> <20170613193124.GQ13873@momjian.us> <87mv98af8j.fsf@seb.koffice.internal> <20170616164600.GO11450@momjian.us> <871sqj9042.fsf@seb.koffice.internal> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 Fri, Jun 16, 2017 at 04:44:46PM -0400, Bruce Momjian wrote: > Yes, that is _exactly_ the right place to look. Only in PG 10 do we > restart the new cluster to invalidate hash indexes. In previous > releases we didn't do the restart. > > That didn't matter with the old rsync instructions, but now that we have > removed the start/stop before rsync step, the final WAL status of > pg_upgrade matters. > > I suggest applying the attached patch Sorry, I meant to say, I suggest applying the attached patch to all Postgres versions, of course modified. While the rsync instructions only appear in PG 9.5+, the instructions work for any supported version of Postgres, so we should allow it to continue working, even if the updated instructions are used. -- 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