From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [COMMITTERS] pgsql: Fix bool/int type confusion |
Date: | 2017-09-22 13:33:36 |
Message-ID: | 15602.1506087216@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-09-22 15:01:05 | pgsql: Assume wcstombs(), towlower(), and sibling functions are always |
Previous Message | Peter Eisentraut | 2017-09-22 13:28:26 | pgsql: Fix build with !USE_WIDE_UPPER_LOWER |
From | Date | Subject | |
---|---|---|---|
Next Message | Sokolov Yura | 2017-09-22 14:15:08 | Re: GUC for cleanup indexes threshold. |
Previous Message | Peter Eisentraut | 2017-09-22 13:29:14 | Re: !USE_WIDE_UPPER_LOWER compile errors in v10+ |