{"push_id":2426044393,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"9a95a77d9d5d3003d2d67121f2731b6e5fc37336","before":"2a0faed9d7028e3830998bd6ca900be651274e27","commits":[{"sha":"9a95a77d9d5d3003d2d67121f2731b6e5fc37336","author":{"name":"Peter Eisentraut","email":"2f47089682e4afbd5de3eea4edffc95dfc1eb9de@gmx.net"},"message":"Use stdbool.h if suitable\n\nUsing the standard bool type provided by C allows some recent compilers\nand debuggers to give better diagnostics.  Also, some extension code and\nthird-party headers are increasingly pulling in stdbool.h, so it's\nprobably saner if everyone uses the same definition.\n\nBut PostgreSQL code is not prepared to handle bool of a size other than\n1, so we keep our own old definition if we encounter a stdbool.h with a\nbool of a different size.  (Among current build farm members, this only\napplies to old macOS versions on PowerPC.)\n\nTo check that the used bool is of the right size, add a static\nassertions about size of GinTernaryValue vs bool.  This is currently the\nonly place that assumes that bool and char are of the same size.\n\nDiscussion: https://www.postgresql.org/message-id/flat/3a0fe7e1-5ed1-414b-9230-53bbc0ed1f49@2ndquadrant.com","distinct":true,"url":"https://api.github.com/repos/Aloisius/postgresql/commits/9a95a77d9d5d3003d2d67121f2731b6e5fc37336"}]}
{"actor":{"display_login":"Aloisius"}}