Re: [COMMITTERS] pgsql: Fix bool/int type confusion
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgreSQL.org
Date: 2017-09-21T18:23:27Z
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
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