{"push_id":3172969666,"size":5,"distinct_size":1,"ref":"refs/heads/commitfest/21/1786","head":"46be3bf8b5b5afe6063512c6ae59514c24b4f7ec","before":"674a2c7fe3918c113013be1561b0e63282532161","commits":[{"sha":"6f19a8c41f976236310a272bb646d3411759e18d","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Teach eval_const_expressions to constant-fold LEAST/GREATEST expressions.\n\nDoing this requires an assumption that the invoked btree comparison\nfunction is immutable.  We could check that explicitly, but in other\nplaces such as contain_mutable_functions we just assume that it's true,\nso we may as well do likewise here.  (If the comparison function's\nbehavior isn't immutable, the sort order in indexes built with it would\nbe unstable, so it seems certainly wrong for it not to be so.)\n\nVik Fearing\n\nDiscussion: https://postgr.es/m/c6e8504c-4c43-35fa-6c8f-3c0b80a912cc@2ndquadrant.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/6f19a8c41f976236310a272bb646d3411759e18d"},{"sha":"b5415e3c2187ab304390524f5ae66b4bd2c58279","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Support parameterized TidPaths.\n\nUp to now we've not worried much about joins where the join key is a\nrelation's CTID column, reasoning that storing a table's CTIDs in some\nother table would be pretty useless.  However, there are use-cases for\nthis sort of query involving self-joins, so that argument doesn't really\nhold water.\n\nThis patch allows generating plans for joins on CTID that use a nestloop\nwith inner TidScan, similar to what we might do with an index on the join\ncolumn.  This is the most efficient way to join when the outer side of\nthe nestloop is expected to yield relatively few rows.\n\nThis change requires upgrading tidpath.c and the generated TidPaths\nto work with RestrictInfos instead of bare qual clauses, but that's\nlong-postponed technical debt anyway.\n\nDiscussion: https://postgr.es/m/17443.1545435266@sss.pgh.pa.us","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/b5415e3c2187ab304390524f5ae66b4bd2c58279"},{"sha":"0a6ea4001a9dff64e9ba66f68855a59a1bf69bc9","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Add a hash opclass for type \"tid\".\n\nUp to now we've not worried much about joins where the join key is a\nrelation's CTID column, reasoning that storing a table's CTIDs in some\nother table would be pretty useless.  However, there are use-cases for\nthis sort of query involving self-joins, so that argument doesn't really\nhold water.\n\nWith larger relations, a merge or hash join is desirable.  We had a btree\nopclass for type \"tid\", allowing merge joins on CTID, but no hash opclass\nso that hash joins weren't possible.  Add the missing infrastructure.\n\nThis also potentially enables hash aggregation on \"tid\", though the\nuse-cases for that aren't too clear.\n\nDiscussion: https://postgr.es/m/1853.1545453106@sss.pgh.pa.us","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/0a6ea4001a9dff64e9ba66f68855a59a1bf69bc9"},{"sha":"60d99797bfb07f8042a8b82c161500f6e4a500ec","author":{"name":"Peter Eisentraut","email":"4b8373d016f277527198385ba72fda0feb5da015@eisentraut.org"},"message":"Change \"checkpoint starting\" message to use \"wal\"\n\nThis catches up with the recent renaming of all user-facing mentions\nof \"xlog\" to \"wal\".\n\nDiscussion: https://www.postgresql.org/message-id/flat/20181129084708.GA9562%40msg.credativ.de","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/60d99797bfb07f8042a8b82c161500f6e4a500ec"},{"sha":"46be3bf8b5b5afe6063512c6ae59514c24b4f7ec","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 21/1786] Progress reporting for pg_verify_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/21/1786\nPatch(es): https://www.postgresql.org/message-id/1545755346.19674.1.camel@credativ.de\nAuthor(s): Bernd Helmle, Michael Banck","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/46be3bf8b5b5afe6063512c6ae59514c24b4f7ec"}]}
{"actor":{"display_login":"postgresql-cfbot"}}