{"push_id":2961940819,"size":8,"distinct_size":3,"ref":"refs/heads/commitfest/20/1062","head":"ffe5cc717e14c853b65d0c7e24d0159f69932f4d","before":"7cdc696cd528540ece408870705602a1fa3148d6","commits":[{"sha":"9274c577f7351c5af8e4c85f4a6031db11c93992","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"Fixes for \"Glyph not available\" warnings from FOP\n\nWith the PostgreSQL 11 release notes acknowledgments list, FOP reported\n\nWARNING: Glyph \"?\" (0x144, nacute) not available in font \"Times-Roman\".\nWARNING: Glyph \"?\" (0x15e, Scedilla) not available in font \"Times-Roman\".\nWARNING: Glyph \"?\" (0x15f, scedilla) not available in font \"Times-Roman\".\nWARNING: Glyph \"?\" (0x131, dotlessi) not available in font \"Times-Roman\".\n\nThis is because we have some new contributors whose names use letters\nthat we haven't used before, and apparently FOP can't handle them out\nof the box.\n\nFor now, just fix this by \"unaccenting\" those names.  In the future,\nmaybe this can be fixed better with a different font configuration.\n\nThere is also another warning\n\nWARNING: Glyph \"?\" (0x3c0, pi) not available in font \"Times-Roman\".\n\nbut that existed in previous releases and is not touched here.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/9274c577f7351c5af8e4c85f4a6031db11c93992"},{"sha":"35584fd05f9b104f057c700360985991f111a847","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"Make spelling of \"acknowledgment\" consistent\n\nI used the preferred U.S. spelling, as we do in other cases.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/35584fd05f9b104f057c700360985991f111a847"},{"sha":"5b75a4f8266a4f187a47929fed0582ee778c703f","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"pgbench: Report errors during run better\n\nWhen an error occurs during a benchmark run, exit with a nonzero exit\ncode and write a message at the end.  Previously, it would just print\nthe error message when it happened but then proceed to print the run\nsummary normally and exit with status 0.  To still allow\ndistinguishing setup from run-time errors, we use exit status 2 for\nthe new state, whereas existing errors during pgbench initialization\nuse exit status 1.\n\nReviewed-by: Fabien COELHO <coelho@cri.ensmp.fr>","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/5b75a4f8266a4f187a47929fed0582ee778c703f"},{"sha":"d48da369ab22a8326d4d3d2b05b574d581057193","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Check for stack overrun in standard_ProcessUtility().\n\nProcessUtility can recurse, and indeed can be driven to infinite\nrecursion, so it ought to have a check_stack_depth() call.  This\ncovers the reported bug (portal trying to execute itself) and a bunch\nof other cases that could perhaps arise somewhere.\n\nPer bug #15428 from Malthe Borch.  Back-patch to all supported branches.\n\nDiscussion: https://postgr.es/m/15428-b3c2915ec470b033@postgresql.org","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/d48da369ab22a8326d4d3d2b05b574d581057193"},{"sha":"e73ca79fc78db4eb13b7f513f16b7164c7b05ba7","author":{"name":"Thomas Munro","email":"1ff054ef0838bf068a4b7c40eef026e560a37025@postgresql.org"},"message":"Move the replication lag tracker into heap memory.\n\nAndres Freund complained about the 128KB of .bss occupied by LagTracker.\nIt's only needed in the walsender process, so allocate it in heap\nmemory there.\n\nAuthor: Thomas Munro\nDiscussion: https://postgr.es/m/20181015200754.7y7zfuzsoux2c4ya%40alap3.anarazel.de","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/e73ca79fc78db4eb13b7f513f16b7164c7b05ba7"},{"sha":"9d906f1119de893a4ca533c5e7b97207a3aa963b","author":{"name":"Andres Freund","email":"883768b6dd2c42aea0031b24be8a2da40fef4b64@anarazel.de"},"message":"Move generic slot support functions from heaptuple.c into execTuples.c.\n\nheaptuple.c was never a particular good fit for slot_getattr(),\nslot_getsomeattrs() and slot_getmissingattrs(), but in upcoming\nchanges slots will be made more abstract (allowing slots that contain\ndifferent types of tuples), making it clearly the wrong place.\n\nNote that slot_deform_tuple() remains in it's current place, as it\nclearly deals with a HeapTuple.  getmissingattrs() also remains, but\nit's less clear that that's correct - but execTuples.c wouldn't be the\nright place.\n\nAuthor: Ashutosh Bapat.\nDiscussion: https://postgr.es/m/20180220224318.gw4oe5jadhpmcdnm@alap3.anarazel.de","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/9d906f1119de893a4ca533c5e7b97207a3aa963b"},{"sha":"c5257345ef61922468cd9abd887c3cb6c38792cb","author":{"name":"Andres Freund","email":"883768b6dd2c42aea0031b24be8a2da40fef4b64@anarazel.de"},"message":"Move TupleTableSlots boolean member into one flag variable.\n\nThere's several reasons for this change:\n1) It reduces the total size of TupleTableSlot / reduces alignment\n   padding, making the commonly accessed members fit into a single\n   cacheline (but we currently do not force proper alignment, so\n   that's not yet guaranteed to be helpful)\n2) Combining the booleans into a flag allows to combine read/writes\n   from memory.\n3) With the upcoming slot abstraction changes, it allows to have core\n   and extended flags, in a memory efficient way.\n\nAuthor: Ashutosh Bapat and Andres Freund\nDiscussion: https://postgr.es/m/20180220224318.gw4oe5jadhpmcdnm@alap3.anarazel.de","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/c5257345ef61922468cd9abd887c3cb6c38792cb"},{"sha":"ffe5cc717e14c853b65d0c7e24d0159f69932f4d","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 20/1062] Generic type subscripting\n\nThis commit was automatically generated by cfbot at commitfest.cputube.org.\nIt is based on patches submitted to the PostgreSQL mailing lists and\nregistered in the PostgreSQL Commitfest application.\n\nThis branch will be overwritten each time a new patch version is posted to\nthe email thread, and also periodically to check for bitrot caused by changes\non the master branch.\n\nCommitfest entry: https://commitfest.postgresql.org/20/1062\nPatch(es): https://www.postgresql.org/message-id/CA+q6zcVq6uvfmk657frfs4XFRO+nuSwEyjvXNScZ+0SH95XJMQ@mail.gmail.com\nAuthor(s): Dmitry Dolgov","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/ffe5cc717e14c853b65d0c7e24d0159f69932f4d"}]}
{"actor":{"display_login":"postgresql-cfbot"}}