Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e344E-0004hr-HS for pgsql-committers@arkaria.postgresql.org; Fri, 13 Oct 2017 17:48: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 1e344E-0004eZ-48 for pgsql-committers@arkaria.postgresql.org; Fri, 13 Oct 2017 17:48: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 1e344D-0004eP-Ko for pgsql-committers@postgresql.org; Fri, 13 Oct 2017 17:48:13 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e344B-0002AH-5t for pgsql-committers@postgresql.org; Fri, 13 Oct 2017 17:48:12 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v9DHm757000531; Fri, 13 Oct 2017 13:48:07 -0400 From: Tom Lane To: Andres Freund cc: Noah Misch , pgsql-committers@postgresql.org Subject: Re: [HACKERS] pgsql: Improve performance of SendRowDescriptionMessage. In-reply-to: <21773.1507908395@sss.pgh.pa.us> References: <307.1507819498@sss.pgh.pa.us> <20171012230844.ye4tnye2shysvqpk@alap3.anarazel.de> <20171013023536.GA492146@rfd.leadboat.com> <12267.1507862660@sss.pgh.pa.us> <20171013070247.GA505228@rfd.leadboat.com> <21773.1507908395@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Fri, 13 Oct 2017 11:26:35 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <529.1507916887.1@sss.pgh.pa.us> Date: Fri, 13 Oct 2017 13:48:07 -0400 Message-ID: <530.1507916887@sss.pgh.pa.us> List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-committers Precedence: bulk Sender: pgsql-committers-owner@postgresql.org I wrote: > Anyway, I will go make the sizeof() usages consistent, just to satisfy > my own uncontrollable neatnik-ism. Assuming that hornet stays red, > which is probable, we should disable "restrict" for that compiler. As expected, that didn't fix it. Andres, are you going to put in a disable? Do we know exactly what we want to test for that? regards, tom lane -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers