{"push_id":2352022877,"size":10,"distinct_size":1,"ref":"refs/heads/commitfest/17/1238","head":"ac3ff4ce549c578a8885dda7c7bcdb43621a5eb5","before":"691f1861338e0a39eaf6275f80a915729f1361fc","commits":[{"sha":"9a5c4f58f36dc7c87619602a7a2ec7de5a287068","author":{"name":"Robert Haas","email":"93159bdbbeed5b47be970d58edfbdf1c3ce55e4c@postgresql.org"},"message":"Try to stabilize EXPLAIN output in partition_check test.\n\nCommit 7d8ac9814bc9bb6df2d845dbabed38d7284c7c2c adjusted these\ntests in the hope of preserving the plan shape, but I failed to\nnotice that the three partitions were, on my local machine, choosing\ntwo different plan shapes.  This is probably related to the fact\nthat all three tables have exactly the same row count.  Try to\nimprove the situation by making pht1_e about half as large as\nthe other two.\n\nPer Tom Lane and the buildfarm.\n\nDiscussion: http://postgr.es/m/25380.1519277713@sss.pgh.pa.us","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/9a5c4f58f36dc7c87619602a7a2ec7de5a287068"},{"sha":"de6428afe13bb6eb1c99a70aada1a105966bc27e","author":{"name":"Robert Haas","email":"93159bdbbeed5b47be970d58edfbdf1c3ce55e4c@postgresql.org"},"message":"Avoid another valgrind complaint about write() of uninitalized bytes.\n\nPeter Geoghegan, per buildfarm member skink and Andres Freund\n\nDiscussion: http://postgr.es/m/20180221053426.gp72lw67yfpzkw7a@alap3.anarazel.de","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/de6428afe13bb6eb1c99a70aada1a105966bc27e"},{"sha":"84cb51b4e24b4e3a7057105971d0d385e179d978","author":{"name":"Robert Haas","email":"93159bdbbeed5b47be970d58edfbdf1c3ce55e4c@postgresql.org"},"message":"postgres_fdw: Fix interaction of PHVs with child joins.\n\nCommit f49842d1ee31b976c681322f76025d7732e860f3 introduced the\nconcept of a child join, but did not update this code accordingly.\n\nAshutosh Bapat, with cosmetic changes by me\n\nDiscussion: http://postgr.es/m/CAFjFpRf=J_KPOtw+bhZeURYkbizr8ufSaXg6gPEF6DKpgH-t6g@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/84cb51b4e24b4e3a7057105971d0d385e179d978"},{"sha":"810e7e264ab547c404e32dba4f8733db53912084","author":{"name":"Robert Haas","email":"93159bdbbeed5b47be970d58edfbdf1c3ce55e4c@postgresql.org"},"message":"Remove extra word from comment.\n\nEtsuro Fujita\n\nDiscussion: http://postgr.es/m/5A8EAF74.5010905@lab.ntt.co.jp","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/810e7e264ab547c404e32dba4f8733db53912084"},{"sha":"edd44738bc88148784899a8949519364d81d9ea8","author":{"name":"Robert Haas","email":"93159bdbbeed5b47be970d58edfbdf1c3ce55e4c@postgresql.org"},"message":"Be lazier about partition tuple routing.\n\nIt's not necessary to fully initialize the executor data structures\nfor partitions to which no tuples are ever routed.  Consider, for\nexample, an INSERT statement that inserts only one row: it only cares\nabout the partition to which that one row is routed.  The new function\nExecInitPartitionInfo performs the initialization in question only\nwhen a particular partition is about to receive a tuple. This includes\ncreating, validating, and saving a pointer to the ResultRelInfo,\nsetting up for speculative insertions, translating WCOs and\ninitializing the resulting expressions, translating returning lists\nand building the appropriate projection information, and setting up a\ntuple conversion map.\n\nOne thing that's not deferred is locking the child partitions; that\nseems desirable but would need more thought.  Still, testing shows\nthat this makes single-row inserts significantly faster on a table\nwith many partitions without harming the bulk-insert case.\n\nAmit Langote, reviewed by Etsuro Fujita, with a few changes by me\n\nDiscussion: http://postgr.es/m/8975331d-d961-cbdd-f862-fdd3d97dc2d0@lab.ntt.co.jp","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/edd44738bc88148784899a8949519364d81d9ea8"},{"sha":"10cfce34c0fe20d2caed5750bbc5c315c0e4cc63","author":{"name":"Peter Eisentraut","email":"2f47089682e4afbd5de3eea4edffc95dfc1eb9de@gmx.net"},"message":"Add user-callable SHA-2 functions\n\nAdd the user-callable functions sha224, sha256, sha384, sha512.  We\nalready had these in the C code to support SCRAM, but there was no test\ncoverage outside of the SCRAM tests.  Adding these as user-callable\nfunctions allows writing some tests.  Also, we have a user-callable md5\nfunction but no more modern alternative, which led to wide use of md5 as\na general-purpose hash function, which leads to occasional complaints\nabout using md5.\n\nAlso mark the existing md5 functions as leak-proof.\n\nReviewed-by: Michael Paquier <michael@paquier.xyz>","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/10cfce34c0fe20d2caed5750bbc5c315c0e4cc63"},{"sha":"0db2fc98cdf4135f9dcfa3740db6f2548682fe7e","author":{"name":"Peter Eisentraut","email":"2f47089682e4afbd5de3eea4edffc95dfc1eb9de@gmx.net"},"message":"Update gratuitous use of MD5 in documentation\n\nIt seems some people are bothered by the outdated MD5 appearing in\nexample code.  So replace it with more modern alternatives or by\na different example function.\n\nReported-by: Jon Wolski <jonwolski@gmail.com>","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/0db2fc98cdf4135f9dcfa3740db6f2548682fe7e"},{"sha":"abcba7001e481a565b8fba2393666dc54e90db61","author":{"name":"Peter Eisentraut","email":"2f47089682e4afbd5de3eea4edffc95dfc1eb9de@gmx.net"},"message":"Fix perlcritic warnings","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/abcba7001e481a565b8fba2393666dc54e90db61"},{"sha":"a6a80134e3bffa0678a82ed7477d9d46dea07d3a","author":{"name":"Robert Haas","email":"93159bdbbeed5b47be970d58edfbdf1c3ce55e4c@postgresql.org"},"message":"Remove extra words.\n\nThomas Munro\n\nDiscussion: http://postgr.es/m/CAEepm=2x3NUSPed6=-wDYs39KtUU5Dw3mK_NAMWps+18FmkApQ@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/a6a80134e3bffa0678a82ed7477d9d46dea07d3a"},{"sha":"ac3ff4ce549c578a8885dda7c7bcdb43621a5eb5","author":{"name":"Commitfest Bot","email":"aab6a594935fe5db0d690bc154b19f642bfbe9d7@cputube.org"},"message":"[CF 17/1238] multivariate MCV lists and histograms\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/17/1238\nPatch(es): https://www.postgresql.org/message-id/651d8a4d-bd9d-087d-e89c-893f8ab1f257%402ndquadrant.com\nAuthor(s): Tomas Vondra","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/ac3ff4ce549c578a8885dda7c7bcdb43621a5eb5"}]}
{"actor":{"display_login":"postgresql-cfbot"}}