{"push_id":2781505781,"size":5,"distinct_size":1,"ref":"refs/heads/commitfest/19/1733","head":"9c4cf08a496b91a69559c26511be2c5fd12b2729","before":"b1353f66ed7ae1a0e46317105ca861896a4c73c3","commits":[{"sha":"5b5ed4756c9b3efff787f4921659a9d4d51726e5","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Ensure pg_dump_sort.c sorts null vs non-null namespace consistently.\n\nThe original coding here (which is, I believe, my fault) supposed that\nit didn't need to concern itself with the possibility that one object\nof a given type-priority has a namespace while another doesn't.  But\nthat's not reliably true anymore, if it ever was; and if it does happen\nthen it's possible that DOTypeNameCompare returns self-inconsistent\ncomparison results.  That leads to unspecified behavior in qsort()\nand a resultant weird output order from pg_dump.\n\nThis should end up being only a cosmetic problem, because any ordering\nconstraints that actually matter should be enforced by the later\ndependency-based sort.  Still, it's a bug, so back-patch.\n\nReport and fix by Jacob Champion, though I editorialized on his\npatch to the extent of making NULL sort after non-NULL, for consistency\nwith our usual sorting definitions.\n\nDiscussion: https://postgr.es/m/CABAq_6Hw+V-Kj7PNfD5tgOaWT_-qaYkc+SRmJkPLeUjYXLdxwQ@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/5b5ed4756c9b3efff787f4921659a9d4d51726e5"},{"sha":"03838b804905e3fd26ec648c7df1505cf0d8e413","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Fix pg_upgrade to handle event triggers in extensions correctly.\n\npg_dump with --binary-upgrade must emit ALTER EXTENSION ADD commands\nfor all objects that are members of extensions.  It forgot to do so for\nevent triggers, as per bug #15310 from Nick Barnes.  Back-patch to 9.3\nwhere event triggers were introduced.\n\nHaribabu Kommi\n\nDiscussion: https://postgr.es/m/153360083872.1395.4593932457718151600@wrigleys.postgresql.org","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/03838b804905e3fd26ec648c7df1505cf0d8e413"},{"sha":"41db97399d6b5492cb4538680531f81f4711b0f4","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Fix incorrect initialization of BackendActivityBuffer.\n\nSince commit c8e8b5a6e, this has been zeroed out using the wrong length.\nIn practice the length would always be too small, leading to not zeroing\nthe whole buffer rather than clobbering additional memory; and that's\npretty harmless, both because shmem would likely start out as zeroes\nand because we'd reinitialize any given entry before use.  Still,\nit's bogus, so fix it.\n\nReported by Petru-Florin Mihancea (bug #15312)\n\nDiscussion: https://postgr.es/m/153363913073.1303.6518849192351268091@wrigleys.postgresql.org","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/41db97399d6b5492cb4538680531f81f4711b0f4"},{"sha":"9b7c56d6cba9d23318d98af58f0c1adc85869bbf","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Don't record FDW user mappings as members of extensions.\n\nCreateUserMapping has a recordDependencyOnCurrentExtension call that's\nbeen there since extensions were introduced (very possibly my fault).\nHowever, there's no support anywhere else for user mappings as members\nof extensions, nor are they listed as a possible member object type in\nthe documentation.  Nor does it really seem like a good idea for user\nmappings to belong to extensions when roles don't.  Hence, remove the\nbogus call.\n\n(As we saw in bug #15310, the lack of any pg_dump support for this case\nensures that any such membership record would silently disappear during\npg_upgrade.  So there's probably no need for us to do anything else\nabout cleaning up after this mistake.)\n\nDiscussion: https://postgr.es/m/27952.1533667213@sss.pgh.pa.us","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/9b7c56d6cba9d23318d98af58f0c1adc85869bbf"},{"sha":"9c4cf08a496b91a69559c26511be2c5fd12b2729","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 19/1733] Online verification of checksums\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/19/1733\nPatch(es): https://www.postgresql.org/message-id/1532606373.3422.5.camel@credativ.de\nAuthor(s): Michael Banck","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/9c4cf08a496b91a69559c26511be2c5fd12b2729"}]}
{"actor":{"display_login":"postgresql-cfbot"}}