{"push_id":2954887423,"size":8,"distinct_size":1,"ref":"refs/heads/commitfest/20/1779","head":"0720c55db0fee83bc04adb9836c640ee726e7fb1","before":"aa8027e327a79bc0526e3ca5788ff0b1c9cfca41","commits":[{"sha":"86896be60ef7ace74b7b6858588ec7fae030fefd","author":{"name":"Andres Freund","email":"883768b6dd2c42aea0031b24be8a2da40fef4b64@anarazel.de"},"message":"Move timeofday() implementation out of nabstime.c.\n\nnabstime.c is about to be removed, but timeofday() isn't related to\nthe rest of the functionality therein, and some find it useful. Move\nto timestamp.c.\n\nDiscussion:\n    https://postgr.es/m/20181009192237.34wjp3nmw7oynmmr@alap3.anarazel.de\n    https://postgr.es/m/20180928223240.kgwc4czzzekrpsid%40alap3.anarazel.de","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/86896be60ef7ace74b7b6858588ec7fae030fefd"},{"sha":"2d10defa7771931295ee804cf096fb9388472a7b","author":{"name":"Andres Freund","email":"883768b6dd2c42aea0031b24be8a2da40fef4b64@anarazel.de"},"message":"Remove timetravel extension.\n\nThe extension depended on old types which are about to be removed. As\nthe code additionally was pretty crufty and didn't provide much in the\nway of functionality, removing the extension seems to be the best way\nforward.  It's fairly trivial to write functionality in plpgsql that\nmore than covers what timetravel did.\n\nAuthor: Andres Freund\nDiscussion:\n    https://postgr.es/m/20171213080506.cwjkpcz3bkk6yz2u@alap3.anarazel.de\n    https://postgr.es/m/25615.1513115237@sss.pgh.pa.us","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/2d10defa7771931295ee804cf096fb9388472a7b"},{"sha":"cda6a8d01d391eab45c4b3e0043a1b2b31072f5f","author":{"name":"Andres Freund","email":"883768b6dd2c42aea0031b24be8a2da40fef4b64@anarazel.de"},"message":"Remove deprecated abstime, reltime, tinterval datatypes.\n\nThese types have been deprecated for a *long* time.\n\nCatversion bump, for obvious reasons.\n\nAuthor: Andres Freund\nDiscussion:\n    https://postgr.es/m/20181009192237.34wjp3nmw7oynmmr@alap3.anarazel.de\n    https://postgr.es/m/20171213080506.cwjkpcz3bkk6yz2u@alap3.anarazel.de\n    https://postgr.es/m/25615.1513115237@sss.pgh.pa.us","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/cda6a8d01d391eab45c4b3e0043a1b2b31072f5f"},{"sha":"b34e84f160a47d9070b304bfc1baf17596d71865","author":{"name":"Michael Paquier","email":"17b9e1c64588c7fa6419b4d29dc1f4426279ba01@paquier.xyz"},"message":"Add TAP tests for pg_verify_checksums\n\nAll options available in the utility get coverage:\n- Tests with disabled page checksums.\n- Tests with enabled test checksums.\n- Emulation of corruption and broken checksums with a full scan and\nsingle relfilenode scan.\n\nThis patch has been contributed mainly by Michael Banck and Magnus\nHagander with things presented on various threads, and I have gathered\nall the contents into a single patch.\n\nAuthor: Michael Banck, Magnus Hagander, Michael Paquier\nReviewed-by: Peter Eisentraut\nDiscussion: https://postgr.es/m/20181005012645.GE1629@paquier.xyz","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/b34e84f160a47d9070b304bfc1baf17596d71865"},{"sha":"f1885386f6246ac7b6f8d3f0aef247988f48ee7a","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Make float exponent output on Windows look the same as elsewhere.\n\nWindows, alone among our supported platforms, likes to emit three-digit\nexponent fields even when two digits would do.  Adjust such results to\nlook like the way everyone else does it.  Eliminate a bunch of variant\nexpected-output files that were needed only because of this quirk.\n\nDiscussion: https://postgr.es/m/2934.1539122454@sss.pgh.pa.us","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/f1885386f6246ac7b6f8d3f0aef247988f48ee7a"},{"sha":"c7d43c4d8a5b7215ea0a32d95260188b5d3ae3f4","author":{"name":"Alvaro Herrera","email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org"},"message":"Correct attach/detach logic for FKs in partitions\n\nThere was no code to handle foreign key constraints on partitioned\ntables in the case of ALTER TABLE DETACH; and if you happened to ATTACH\na partition that already had an equivalent constraint, that one was\nignored and a new constraint was created.  Adding this to the fact that\nforeign key cloning reuses the constraint name on the partition instead\nof generating a new name (as it probably should, to cater to SQL\nstandard rules about constraint naming within schemas), the result was a\npretty poor user experience -- the most visible failure was that just\ndetaching a partition and re-attaching it failed with an error such as\n\n  ERROR:  duplicate key value violates unique constraint \"pg_constraint_conrelid_contypid_conname_index\"\n  DETAIL:  Key (conrelid, contypid, conname)=(26702, 0, test_result_asset_id_fkey) already exists.\n\nbecause it would try to create an identically-named constraint in the\npartition.  To make matters worse, if you tried to drop the constraint\nin the now-independent partition, that would fail because the constraint\nwas still seen as dependent on the constraint in its former parent\npartitioned table:\n  ERROR:  cannot drop inherited constraint \"test_result_asset_id_fkey\" of relation \"test_result_cbsystem_0001_0050_monthly_2018_09\"\n\nThis fix attacks the problem from two angles: first, when the partition\nis detached, the constraint is also marked as independent, so the drop\nnow works.  Second, when the partition is re-attached, we scan existing\nconstraints searching for one matching the FK in the parent, and if one\nexists, we link that one to the parent constraint.  So we don't end up\nwith a duplicate -- and better yet, we don't need to scan the referenced\ntable to verify that the constraint holds.\n\nTo implement this I made a small change to previously planner-only\nstruct ForeignKeyCacheInfo to contain the constraint OID; also relcache\nnow maintains the list of FKs for partitioned tables too.\n\nBackpatch to 11.\n\nReported-by: Michael Vitale (bug #15425)\nDiscussion: https://postgr.es/m/15425-2dbc9d2aa999f816@postgresql.org","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/c7d43c4d8a5b7215ea0a32d95260188b5d3ae3f4"},{"sha":"24a2c436a5ce1912373a6c9561cbabd09495552d","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Remove dead reference to ecpg resultmap file.\n\nI missed this in my prior commit because it doesn't matter in non-VPATH\nbuilds.\n\nPer buildfarm.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/24a2c436a5ce1912373a6c9561cbabd09495552d"},{"sha":"0720c55db0fee83bc04adb9836c640ee726e7fb1","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 20/1779] CLUSTER command progress monitor\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/20/1779\nPatch(es): https://www.postgresql.org/message-id/3ec1c97a-6293-237a-4e49-1b16a7a33273@lab.ntt.co.jp\nAuthor(s): Tatsuro Yamada","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/0720c55db0fee83bc04adb9836c640ee726e7fb1"}]}
{"actor":{"display_login":"postgresql-cfbot"}}