Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dv68H-0001RI-Pe for pgsql-hackers@arkaria.postgresql.org; Thu, 21 Sep 2017 18:23:29 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dv68H-0007PQ-CE for pgsql-hackers@arkaria.postgresql.org; Thu, 21 Sep 2017 18:23:29 +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 1dv68F-0007N6-Es for pgsql-hackers@postgreSQL.org; Thu, 21 Sep 2017 18:23:27 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dv68C-0003qD-LC for pgsql-hackers@postgreSQL.org; Thu, 21 Sep 2017 18:23:27 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 81CA920A9E; Thu, 21 Sep 2017 14:23:23 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Thu, 21 Sep 2017 14:23:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=fprPqSuzRyNXQB1a0TSuZ75cHTJYkGS2eHqQq7btJ3E=; b=jgjlBmbv XQBIWbKbiNrweNkoCPaHDPCloLww2O9Xekfk1GxHKCkjm6QP7or21mJf3GewA+hv b+tII3E6jprs6kl3XgVTO0hbbe3Uo2NgxM2YeYML78AGgbU70Od5E4LlLS9fIFL3 J4eHkClgBkG1SRHz8Z7ogZHN5A263judk2i0ja/o48j+aiG1pCUtDzAEWRM8qkFS ycyNowGgQKqB6EUto0Ubc1aqBmh8L2nRvJCuBxpGQmGp4HDKzK4AFK0OOymEZ+BP Rsl8SVXuvOrAQVa9X3CSF9HJLlxsMStUODNFf+1aytcl48ScO6X3B+jAbHuHGQza Y4RJA2WvJEl17Q== X-ME-Sender: X-Sasl-enc: Oc5XJWbsZ4Q0TwrzUvTumm0ZuImUkv2d6gNk9k3q8p0o 1506018203 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 366F67ECBA; Thu, 21 Sep 2017 14:23:23 -0400 (EDT) Subject: Re: [COMMITTERS] pgsql: Fix bool/int type confusion To: Tom Lane References: <20053.1506008800@sss.pgh.pa.us> Cc: pgsql-hackers@postgreSQL.org From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <6f69d4e1-647e-4f05-28a8-117388d3bfe9@2ndquadrant.com> Date: Thu, 21 Sep 2017 14:23:27 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20053.1506008800@sss.pgh.pa.us> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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 9/21/17 11:46, Tom Lane wrote: > So the code in their git repo still has the variable as bool, but > there's no ++ operator on it anymore. > > This also means that the portability problem is purely hypothetical; > given valid tz reference data the code wouldn't ever try to increment > "hit" to 2 anyway. It's even more hypothetical for us, because we don't > use leap-second-aware zones. It's not so much that there is an actual portability problem. The problem is that the compiler issues a warning for this with stdbool. > Therefore, what I would like to do is revert this commit (0ec2e908b), > and then either leave the problem to be fixed by our next regular sync > with a released tzcode version, or else force a sync with their git tip > to absorb their fix now. In either case we should keep all our live > branches in sync. I'm willing to do the code-sync work either way. That makes sense. There is no urgency on the stdbool patch set, so waiting for this to be resolved properly around November seems reasonable. -- 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