{"push_id":3166759051,"size":7,"distinct_size":1,"ref":"refs/heads/commitfest/21/1857","head":"58af0f9d748850c45d802f0f1472435e86dde3a2","before":"d2c0ad4e41d79bdc9c59400b38a3484445ddeaf6","commits":[{"sha":"e9fcfed3fb6b15e6b33bea9bb8504b14560857a8","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Fix portability failure introduced in commits d2b0b60e7 et al.\n\nI made a frontend fprintf() format use %m, forgetting that that's only\nsafe in HEAD not the back branches; prior to 96bf88d52 and d6c55de1f,\nit would work on glibc platforms but not elsewhere.  Revert to using\n%s ... strerror(errno) as the code did before.\n\nWe could have left HEAD as-is, but for code consistency across branches,\nI chose to apply this patch there too.\n\nPer Coverity and a few buildfarm members.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/e9fcfed3fb6b15e6b33bea9bb8504b14560857a8"},{"sha":"8528e3d849a896f8711c56fb41eae56f8c986729","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Fix failure to check for open() or fsync() failures.\n\nWhile it seems OK to not be concerned about fsync() failure for a\npre-existing signal file, it's not OK to not even check for open()\nfailure.  This at least causes complaints from static analyzers,\nand I think on some platforms passing -1 to fsync() or close() might\ntrigger assertion-type failures.  Also add (void) casts to make clear\nthat we're ignoring fsync's result intentionally.\n\nOversights in commit 2dedf4d9a, noted by Coverity.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/8528e3d849a896f8711c56fb41eae56f8c986729"},{"sha":"1e504f01da11db0181d7b28bb30cb5eeb0767184","author":{"name":"Michael Paquier","email":"17b9e1c64588c7fa6419b4d29dc1f4426279ba01@paquier.xyz"},"message":"Ignore inherited temp relations from other sessions when truncating\n\nInheritance trees can include temporary tables if the parent is\npermanent, which makes possible the presence of multiple temporary\nchildren from different sessions.  Trying to issue a TRUNCATE on the\nparent in this scenario causes a failure, so similarly to any other\nqueries just ignore such cases, which makes TRUNCATE work\ntransparently.\n\nThis makes truncation behave similarly to any other DML query working on\nthe parent table with queries which need to be work on the children.  A\nset of isolation tests is added to cover basic cases.\n\nReported-by: Zhou Digoal\nAuthor: Amit Langote, Michael Paquier\nDiscussion: https://postgr.es/m/15565-ce67a48d0244436a@postgresql.org\nBackpatch-through: 9.4","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/1e504f01da11db0181d7b28bb30cb5eeb0767184"},{"sha":"b450abd2551ee30b5bc289c662f5728d87e13a39","author":{"name":"Alexander Korotkov","email":"1c137998207470ad0f56303c4fc305487ec0232f@postgresql.org"},"message":"Remove entry tree root conflict checking from GIN predicate locking\n\nAccording to README we acquire predicate locks on entry tree leafs and posting\ntree roots.  However, when ginFindLeafPage() is going to lock leaf in exclusive\nmode, then it checks root for conflicts regardless whether it's a entry or\nposting tree.  Assuming that we never place predicate lock on entry tree root\n(excluding corner case when root is leaf), this check is redundant.  This\ncommit removes this check.  Now, root conflict checking is controlled by\nseparate argument of ginFindLeafPage().\n\nDiscussion: https://postgr.es/m/CAPpHfdv7rrDyy%3DMgsaK-L9kk0AH7az0B-mdC3w3p0FSb9uoyEg%40mail.gmail.com\nAuthor: Alexander Korotkov\nBackpatch-through: 11","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/b450abd2551ee30b5bc289c662f5728d87e13a39"},{"sha":"5c828307973366f424438b848d4cca6ef98c032e","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"pg_dump: Add missing newline to error message","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/5c828307973366f424438b848d4cca6ef98c032e"},{"sha":"ae4472c619341ff0517254d395d74796277622e6","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"Remove obsolete IndexIs* macros\n\nRemove IndexIsValid(), IndexIsReady(), IndexIsLive() in favor of\naccessing the index structure directly.  These macros haven't been\nused consistently, and the original reason of maintaining source\ncompatibility with PostgreSQL 9.2 is gone.\n\nDiscussion: https://www.postgresql.org/message-id/flat/d419147c-09d4-6196-5d9d-0234b230880a%402ndquadrant.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/ae4472c619341ff0517254d395d74796277622e6"},{"sha":"58af0f9d748850c45d802f0f1472435e86dde3a2","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 21/1857] Installation instructions update (pg_ctl)\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/1857\nPatch(es): https://www.postgresql.org/message-id/f4f21f14-7523-8be1-37ee-e7c2478a696d@pgug.de\nAuthor(s): Andreas &#39;ads&#39; Scherbaum","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/58af0f9d748850c45d802f0f1472435e86dde3a2"}]}
{"actor":{"display_login":"postgresql-cfbot"}}