From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
cc: pgsql-hackers@postgreSQL.org
Subject: Re: [COMMITTERS] pgsql: Fix bool/int type confusion
In-reply-to: <0ce7a937-a938-0517-cb32-6401f3befe38@2ndquadrant.com>
References: <E1dsWhf-0000pT-F9@gemulon.postgresql.org>
 <20053.1506008800@sss.pgh.pa.us>
 <6f69d4e1-647e-4f05-28a8-117388d3bfe9@2ndquadrant.com>
 <27597.1506020289@sss.pgh.pa.us>
 <0ce7a937-a938-0517-cb32-6401f3befe38@2ndquadrant.com>
Comments: In-reply-to Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
	message dated "Fri, 22 Sep 2017 08:56:39 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <15601.1506087216.1@sss.pgh.pa.us>
Date: Fri, 22 Sep 2017 09:33:36 -0400
Message-ID: <15602.1506087216@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> On 9/21/17 14:58, Tom Lane wrote:
>> I've just been going through their git commit log to see what else has
>> changed since tzcode2017b, and I note that there are half a dozen other
>> portability-ish fixes.  I think that some of them affect only code we
>> don't use, but I'm not sure that that's the case for all.  So I'm a bit
>> inclined to go with plan B, that is sync with their current HEAD now.

> I suppose it might be good to do this after 10.0 final is wrapped?

I went and did it already.  I'm not particularly worried about the
impending 10.0 wrap --- the changes are minor as such things go,
and we've generally not worried about giving previous tzcode syncs
more than a few days' buildfarm testing before shipping them.

			regards, tom lane


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers