Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dQOxG-0007Sv-JY for pgsql-hackers@arkaria.postgresql.org; Thu, 29 Jun 2017 02:13:14 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dQOxG-0005zW-6T for pgsql-hackers@arkaria.postgresql.org; Thu, 29 Jun 2017 02:13:14 +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 1dQOvi-0002EN-SN for pgsql-hackers@postgresql.org; Thu, 29 Jun 2017 02:11:39 +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 1dQOvg-0003b5-CR for pgsql-hackers@postgresql.org; Thu, 29 Jun 2017 02:11:37 +0000 Received: from bruce by momjian.us with local (Exim 4.84_2) (envelope-from ) id 1dQOvf-0004yx-Ef; Wed, 28 Jun 2017 22:11:35 -0400 Date: Wed, 28 Jun 2017 22:11:35 -0400 From: Bruce Momjian To: Sergey Burladyan Cc: Amit Kapila , PostgreSQL-development , Dmitriy Sarafannikov , Vladimir Borodin Subject: Re: Broken hint bits (freeze) Message-ID: <20170629021135.GD16576@momjian.us> References: <20170620025919.GA28277@momjian.us> <20170620033726.GB28277@momjian.us> <87h8zb6kbx.fsf@seb.koffice.internal> <8760fq7pfe.fsf@seb.koffice.internal> <20170621163356.GB9358@momjian.us> <87lgoi68dg.fsf@seb.koffice.internal> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87lgoi68dg.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 Fri, Jun 23, 2017 at 06:17:47PM +0300, Sergey Burladyan wrote: > PS: > I successfully upgraded last night from 9.2 to 9.4 and find other issue :-) > > It is about hash index and promote: > 1. create master > 2. create standby from it > 3. create unlogged table and hash index like: > create unlogged table test (id int primary key, v text); > create index on test using hash (id); > 3. stop master > 4. promote standby > > now, if you try to upgrade this new promoted master pg_upgrade will stop > on this hash index: > error while creating link for relation "public.test_id_idx" ("s/9.2/base/16384/16393" to "m/9.4/base/16422/16393"): No such file or directory > Failure, exiting > > I touch this file (s/9.2/base/16384/16393) and rerun pg_upgrade from > scratch and it complete successfully. Sergey, can you please test if the table "test" is not unlogged, does pg_upgrade still fail on the hash index file? -- 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