{"push_id":3935628965,"size":3,"distinct_size":1,"ref":"refs/heads/commitfest/24/2112","head":"a3454bb91661801fc59d5b7c3475d4d6e0bf81d1","before":"9ae8dc25d041a9e42b4ccf0980a65f61c5827680","commits":[{"sha":"9be4ce4fa33594e035eb421894247e5af61393ce","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Make deadlock-parallel isolation test more robust.\n\nThis test failed fairly reproducibly on some CLOBBER_CACHE_ALWAYS\nbuildfarm animals.  The cause seems to be that if a parallel worker\nis slow enough to reach its lock wait, it may not be released by\nthe first deadlock check run, and then later deadlock checks might\ndecide to unblock the d2 session instead of the d1 session, leaving\nus in an undetected deadlock state (since the isolationtester client\nis waiting for d1 to complete first).\n\nFix by introducing an additional lock wait at the end of the d2a1\nstep, ensuring that the deadlock checker will recognize that d1\nhas to be unblocked before d2a1 completes.\n\nAlso reduce max_parallel_workers_per_gather to 3 in this test.  With the\ndefault max_worker_processes value, we were only getting one parallel\nworker for the d2a1 step, which is not the case I hoped to test.  We\nshould get 3 for d1a2 and 2 for d2a1, as the code stands; and maybe 3\nfor d2a1 if somebody figures out why the last parallel worker slot isn't\nfree already.\n\nDiscussion: https://postgr.es/m/22195.1566077308@sss.pgh.pa.us","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/9be4ce4fa33594e035eb421894247e5af61393ce"},{"sha":"7e78c872dd5b0f53bbeed90c2b6e610c14e9be4b","author":{"name":"Peter Eisentraut","email":"4b8373d016f277527198385ba72fda0feb5da015@eisentraut.org"},"message":"Remove obsolete reference to Irix","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/7e78c872dd5b0f53bbeed90c2b6e610c14e9be4b"},{"sha":"a3454bb91661801fc59d5b7c3475d4d6e0bf81d1","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 24/2112] range_agg\n\nThis commit was automatically generated by a robot at cfbot.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/24/2112\nPatch(es): https://www.postgresql.org/message-id/CA+renyV+ER5HXjFmw=JnOfX_ZeMWjECA9VPjCQ+fF23QFVTYGA@mail.gmail.com\nAuthor(s): Paul Jungwirth","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/a3454bb91661801fc59d5b7c3475d4d6e0bf81d1"}]}
{"actor":{"display_login":"postgresql-cfbot"}}