Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c1zYt-00056H-Mg for pgsql-hackers@arkaria.postgresql.org; Wed, 02 Nov 2016 17:42:55 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1c1zYt-0000aZ-6F for pgsql-hackers@arkaria.postgresql.org; Wed, 02 Nov 2016 17:42:55 +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 1c1zYs-0000aS-ON for pgsql-hackers@postgresql.org; Wed, 02 Nov 2016 17:42:54 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1c1zYp-000193-UJ for pgsql-hackers@postgresql.org; Wed, 02 Nov 2016 17:42:53 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 81DFC2097E; Wed, 2 Nov 2016 13:42:50 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute2.internal (MEProxy); Wed, 02 Nov 2016 13:42:50 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=x-me-sender:x-sasl-enc:subject:to :references:cc:from:message-id:date:mime-version:in-reply-to :content-type:content-transfer-encoding; s=smtpout; bh=G06abzWSM zLf2ssd5AOFMc1iLgE=; b=UqVpfaBfa+echPUDXh2hYBxr+6J1UFj7yGATOdbfg sEvY1KpKF+cTS/UcQ+qOXi1bXbEUMYu2P865HyMMmvCjSuMA0ampUTD58GQSvmKy Z0A7TE8rOeZKI5t6TPD8kwpuZbZbUUr9CmiTPeUPEZBcppfZ73sw1ISsNtrJLX48 fM= X-ME-Sender: X-Sasl-enc: IvpmCcXyiakDcHVKAtQJKp4h54f4G5C63uo3rgeJwpV6 1478108570 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id E8E15CCF29; Wed, 2 Nov 2016 13:42:49 -0400 (EDT) Subject: Re: pageinspect: Hash index support To: Jesper Pedersen References: <5d64a536-cc90-ce96-b68f-5b6bd3206476@redhat.com> <80a00b5c-56d3-dffb-8dba-edf5d2167b12@2ndquadrant.com> <16d89e7e-cb1a-cb5d-e944-6f10c324a312@redhat.com> <836487ee-8d4e-cd49-54ac-f4793ddba5ae@redhat.com> <8a751498-6ee9-b943-abf3-b5641851d7de@2ndquadrant.com> <62ee2eba-3a5b-06d3-e224-cfe00b395be7@redhat.com> <66afc31d-e97a-41c3-da4c-bfa02fa2d54e@redhat.com> Cc: Michael Paquier , Ashutosh Sharma , Jeff Janes , Alvaro Herrera , PostgreSQL Hackers From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <02dc6cef-a80c-c976-8ac0-518ff9b22dd8@2ndquadrant.com> Date: Wed, 2 Nov 2016 13:42:49 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.6 (--) 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 11/1/16 3:28 PM, Peter Eisentraut wrote: > I have also committed the tests > that I proposed and will work through the failures. So, we're down to crashes in gin_metapage_info() on ia64 and sparc64. My guess is that the raw page data that is passed into the function needs to be 8-byte aligned before being accessed as GinMetaPageData. (Maybe GinPageGetMeta() should do it?) Does anyone have a box like this handy to experiment? Of course an actual core dump could tell more. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers