{"push_id":2035833345,"size":3,"distinct_size":1,"ref":"refs/heads/commitfest/15/528","head":"c745aee4756a388a1f64cb3b61164b915ec34676","before":"f2af80f12375cf0aff66f74d74299ba72df0e525","commits":[{"sha":"1fdab4d5aa47d8a2bb29ccb1122b0158f6db221f","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Clean up sloppy maintenance of regression test schedule files.\n\nThe partition_join test was added to a parallel group that was already\nat the maximum of 20 concurrent tests.  The hash_func test wasn't\nadded to serial_schedule at all.  The identity and partition_join tests\nwere added to serial_schedule with the aid of a dartboard, rather than\nmaintaining consistency with parallel_schedule.\n\nThere are proposals afoot to make these sorts of errors harder to make,\nbut in the meantime let's fix the ones already in place.\n\nDiscussion: https://postgr.es/m/a37e9c57-22d4-1b82-1270-4501cd2e984e@2ndquadrant.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/1fdab4d5aa47d8a2bb29ccb1122b0158f6db221f"},{"sha":"ef73a8162a5fe9c4b2f895bf9fb660f1aabc796c","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Enforce our convention about max number of parallel regression tests.\n\nWe have a very old rule that parallel_schedule should have no more\nthan twenty tests in any one parallel group, so as to provide a\nbound on the number of concurrently running processes needed to\npass the tests.  But people keep forgetting the rule, so let's add\na few lines of code to check it.\n\nDiscussion: https://postgr.es/m/a37e9c57-22d4-1b82-1270-4501cd2e984e@2ndquadrant.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/ef73a8162a5fe9c4b2f895bf9fb660f1aabc796c"},{"sha":"c745aee4756a388a1f64cb3b61164b915ec34676","author":{"name":"Commitfest Bot","email":"aab6a594935fe5db0d690bc154b19f642bfbe9d7@cputube.org"},"message":"[CF 15/528] Fix the optimization to skip WAL-logging on table created in same transaction\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 or the master branch changes.\n\nCommitfest entry: https://commitfest.postgresql.org/15/528\nPatch(es): https://www.postgresql.org/message-id/20170914.153459.94374240.horiguchi.kyotaro%40lab.ntt.co.jp\nAuthor(s): Heikki Linnakangas, Michael Paquier, Kyotaro Horiguchi","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/c745aee4756a388a1f64cb3b61164b915ec34676"}]}
{"actor":{"display_login":"postgresql-cfbot"}}