{"push_id":2700737799,"size":7,"distinct_size":1,"ref":"refs/heads/commitfest/18/1574","head":"c2fb3c68176d4bfe8adf86f53d6f41abafa4326a","before":"920c9a24cd64bb8f347d3551b3763edf5d432f6c","commits":[{"sha":"8d1c1ca70b012594932578a0994a5d45f29d9572","author":{"name":"Alvaro Herrera","email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org"},"message":"Reduce cost of test_decoding's new oldest_xmin test\n\nChange a whole-database VACUUM into doing just pg_attribute, which is\nthe portion that verifies what we want it to do.  The original\nformulation wastes a lot of CPU time, which leads the test to fail when\nruntime exceeds isolationtester timeout when it's super-slow, such as\nunder CLOBBER_CACHE_ALWAYS.  Per buildfarm member friarbird.\n\nIt turns out that the previous shape of the test doesn't always detect\nthe condition it is supposed to detect (on unpatched reorderbuffer\ncode): the reason is that there is a good chance of encountering a\nxl_running_xacts record (logged every 15 seconds) before the checkpoint\n-- and because we advance the xmin when we receive that WAL record, and\nwe *don't* advance the xmin twice consecutively without receiving a\nclient message in between, that means the xmin is not advanced enough\nfor the tuple to be pruned from pg_attribute by VACUUM.  So the test\nwould spuriously pass.\n\nThe reason this test deficiency wasn't detected earlier is that HOT\npruning removes the tuple anyway, even if vacuum leaves it in place, so\nthe test correctly fails (detecting the coding mistake), but for the\nwrong reason.\n\nTo fix this mess, run the s0_get_changes step twice before vacuum\ninstead of once: this seems to cause the xmin to be advanced reliably,\nwreaking havoc with more certainty.\n\nAuthor: Arseny Sher\nDiscussion: https://postgr.es/m/87h8lkuxoa.fsf@ars-thinkpad","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/8d1c1ca70b012594932578a0994a5d45f29d9572"},{"sha":"17411e0ffa1e2a9789756203019dce368ad4bf60","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"doc: Fix typos\n\nAuthor: Justin Pryzby <pryzby@telsasoft.com>","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/17411e0ffa1e2a9789756203019dce368ad4bf60"},{"sha":"0c06534bd63b0bd23d7744a53f3b490a2adeea8a","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"doc: Reword old inheritance partitioning documentation\n\nPrefer to use phrases like \"child\" instead of \"partition\" when\ndescribing the legacy inheritance-based partitioning.  The word\n\"partition\" now has a fixed meaning for the built-in partitioning, so\nkeeping it out of the documentation of the old method makes things\nclearer.\n\nAuthor: Justin Pryzby <pryzby@telsasoft.com>","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/0c06534bd63b0bd23d7744a53f3b490a2adeea8a"},{"sha":"3ca966c06f91fb6ccc11d71d4094c1e297b8945d","author":{"name":"Alvaro Herrera","email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org"},"message":"logical decoding: beware of an unset specinsert change\n\nCoverity complains that there is no protection in the code (at least in\nnon-assertion-enabled builds) against speculative insertion failing to\nfollow the expected protocol.  Add an elog(ERROR) for the case.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/3ca966c06f91fb6ccc11d71d4094c1e297b8945d"},{"sha":"4513d3a4be0bb7d0141f8b7eaf669a55c08e41b0","author":{"name":"Jeff Davis","email":"a6043a059331789899fcd6238d9fdd7ab2ab417a@postgresql.org"},"message":"Add test for partitionwise join involving default partition.\n\nAuthor: Rajkumar Raghuwanshi\nReviewed-by: Ashutosh Bapat\nDiscussion: https://postgr.es/m/CAKcux6ky5YeZAY74qSh-ayPZZEQchz092g71iXXbC0%2BE3xoscA%40mail.gmail.com\nDiscussion: https://postgr.es/m/CAKcux6kOQ85Xtzxu3tM1mR7Vk%3D7Z2e4rG7dL1iMZqPgLMpxQYg%40mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/4513d3a4be0bb7d0141f8b7eaf669a55c08e41b0"},{"sha":"8fb68aa2655762beed237ea04e2c6c490cf1ed10","author":{"name":"Andrew Dunstan","email":"02e0a999c50b1f88df7a8f5a04e1b76b35ea6a88@dunslane.net"},"message":"Print DEBUG2 like that rather than as DEBUG\n\nDEBUG is an alias for DEBUG2, but we want DEBUG2 to show in the settings\nno matter how it was spelled.\n\nTakeshi Ideriha\n\nDiscussion: https://postgr.es/m/4E72940DA2BF16479384A86D54D0988A5678EC03@G01JPEXMBKW04","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/8fb68aa2655762beed237ea04e2c6c490cf1ed10"},{"sha":"c2fb3c68176d4bfe8adf86f53d6f41abafa4326a","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 18/1574] Transactions involving multiple postgres foreign servers\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/18/1574\nPatch(es): https://www.postgresql.org/message-id/CAD21AoDTAGj5MohEPQps0GjmF413pO9uwykqZ36g7JMh0a+UjA@mail.gmail.com\nAuthor(s): Masahiko Sawada, Ashutosh Bapat","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/c2fb3c68176d4bfe8adf86f53d6f41abafa4326a"}]}
{"actor":{"display_login":"postgresql-cfbot"}}