{"push_id":3115874757,"size":3,"distinct_size":1,"ref":"refs/heads/commitfest/21/1821","head":"9003599495ef272d3e7c976947d3af6d7278e45b","before":"df227dfb5ecab63c4b5ea4f86aaed9629bbf6237","commits":[{"sha":"d2b0b60e71931997455afd5da72ca29148f1ca51","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Improve our response to invalid format strings, and detect more cases.\n\nPlaces that are testing for *printf failure ought to include the format\nstring in their error reports, since bad-format-string is one of the\nmore likely causes of such failure.  This both makes it easier to find\nand repair the mistake, and provides at least some useful info to the\nuser who stumbles across such a problem.\n\nAlso, tighten snprintf.c to report EINVAL for an invalid flag or\nfinal character in a format %-spec (including the case where the\n%-spec is missing a final character altogether).  This seems like\nbetter project policy, and it also allows removing an instruction\nor two from the hot code path.\n\nBack-patch the error reporting change in pvsnprintf, since it should be\nharmless and may be helpful; but not the snprintf.c change.\n\nPer discussion of bug #15511 from Ertuğrul Kahveci, which reported an\ninvalid translated format string.  These changes don't fix that error,\nbut they should improve matters next time we make such a mistake.\n\nDiscussion: https://postgr.es/m/15511-1d8b6a0bc874112f@postgresql.org","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/d2b0b60e71931997455afd5da72ca29148f1ca51"},{"sha":"730422afcdb6784bbe20efc65de72156d470b0c4","author":{"name":"Michael Paquier","email":"17b9e1c64588c7fa6419b4d29dc1f4426279ba01@paquier.xyz"},"message":"Fix some errhint and errdetail strings missing a period\n\nAs per the error message style guide of the documentation, those should\nbe full sentences.\n\nAuthor: Daniel Gustafsson\nReviewed-by: Michael Paquier, Álvaro Herrera\nDiscussion: https://1E8D49B4-16BC-4420-B4ED-58501D9E076B@yesql.se","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/730422afcdb6784bbe20efc65de72156d470b0c4"},{"sha":"9003599495ef272d3e7c976947d3af6d7278e45b","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 21/1821] Avoid creation of the free space map for small tables\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/21/1821\nPatch(es): https://www.postgresql.org/message-id/CAJVSVGWR8mH8HKYaxNw3r9_trXXcwEYoW_sst8XbK_dZi_KNuw@mail.gmail.com\nAuthor(s): John Naylor","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/9003599495ef272d3e7c976947d3af6d7278e45b"}]}
{"actor":{"display_login":"postgresql-cfbot"}}