Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e34d2-0006b4-Ja for pgsql-committers@arkaria.postgresql.org; Fri, 13 Oct 2017 18:24:12 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e34d2-0002HD-1o for pgsql-committers@arkaria.postgresql.org; Fri, 13 Oct 2017 18:24:12 +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 1e34d1-0002Ga-HC for pgsql-committers@postgresql.org; Fri, 13 Oct 2017 18:24:11 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e34cy-0004ZM-Fx for pgsql-committers@postgresql.org; Fri, 13 Oct 2017 18:24:11 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 174C220D68; Fri, 13 Oct 2017 14:24:07 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Fri, 13 Oct 2017 14:24:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=fbKbfyCmEgDBehmsOuhBp9048JmaX 7/LmPyTuBgeHoo=; b=IKwOlqxqhzNmgAY7AgZl2FcEypJjOrORXddpdErgFQpG5 FRYCcPKOfofW5TKfT/y0AVHVVk+Mj4o93DgGdTS9Vx0Rs7f1BAdk1V1xsREyIfZp JRGWP5ifcDW0Vw6I8Brng/hyXZLUQB4MZqZUWyYGcrzUu4xth24u9ZOCICG6fM3q cGXrQMwqO/h4gtIgIC4Od8S5ulXeGCvohC0Qut659MIh5RhJ/2fZrZWxMMw5+Ce9 aNhZPw8l8XZHS7TWSJunEXb0+OJPGhcRd8Vb49IkMzZNzcS3LhEhkqbxTNj8mGKo 2J4EGziOTbIMuxa3ZtLcX0fxWnTuI6pCTGCrR0yGQ== X-ME-Sender: Received: from intern.anarazel.de (unknown [136.24.76.72]) by mail.messagingengine.com (Postfix) with ESMTPA id C93C624767; Fri, 13 Oct 2017 14:24:06 -0400 (EDT) Date: Fri, 13 Oct 2017 11:24:05 -0700 From: Andres Freund To: Tom Lane Cc: Noah Misch , pgsql-committers@postgresql.org Subject: Re: [HACKERS] pgsql: Improve performance of SendRowDescriptionMessage. Message-ID: <20171013182405.7smzzv3vw67o2fjy@alap3.anarazel.de> 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> <530.1507916887@sss.pgh.pa.us> <20171013180106.ruju5qtn6xpw45us@alap3.anarazel.de> <1820.1507918762@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1820.1507918762@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 On 2017-10-13 14:19:22 -0400, Tom Lane wrote: > > So it'd probably better to introduce a FORCE_DISABLE_RESTRICT=yes, set > > at the same place, that's then tested before running the relevant > > configure check? > > +1. I think you don't actually have to skip the configure check, > and there might be some value in letting it carry on normally > (so that "restrict" is set properly). We'd just want it to affect > what pg_restrict gets defined as. Something like > if test "$ac_cv_c_restrict" = "no" -o "x$FORCE_DISABLE_RESTRICT" = "xyes"; then > pg_restrict="" > else > pg_restrict="$ac_cv_c_restrict" Yea, that works. Will make it so. Greetings, Andres Freund -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers