Re: [COMMITTERS] pgsql: Fix bool/int type confusion
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-hackers@postgreSQL.org
Date: 2017-09-22T13:33:36Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Sync our copy of the timezone library with IANA tzcode master.
- 47f849a3c900 11.0 landed
- e25f4401dad7 9.6.6 landed
- dbd6099fbc77 9.4.15 landed
- a07105afacba 9.2.24 landed
- 89f02e17a6ac 9.5.10 landed
- 3876b16ce3f3 10.0 landed
- 2020f90bf675 9.3.20 landed
- 7afafe8af36c 9.6.2 cited
-
Fix bool/int type confusion
- 0ec2e908babf 11.0 cited
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