{"push_id":2880583193,"size":4,"distinct_size":1,"ref":"refs/heads/commitfest/19/1705","head":"d58c7899bbf6772df43c681ba220daebe61b8382","before":"0846cc27df41125239954b76d4c2ace015a15999","commits":[{"sha":"6b78231d918bba1b99d15e0bf19753bd8f826222","author":{"name":"Alvaro Herrera","email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org"},"message":"Move PartitionDispatchData struct definition to execPartition.c\n\nThere's no reason to expose the struct definition, so don't.\n\nAuthor: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>\nDiscussion: https://postgr.es/m/d3fa24c1-bc65-7133-81df-6474387ccc4f@lab.ntt.co.jp","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/6b78231d918bba1b99d15e0bf19753bd8f826222"},{"sha":"1f4a920b7309499d2d0c4ceda5e6356e10bc51da","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Fix failure with initplans used conditionally during EvalPlanQual rechecks.\n\nThe EvalPlanQual machinery assumes that any initplans (that is,\nuncorrelated sub-selects) used during an EPQ recheck would have already\nbeen evaluated during the main query; this is implicit in the fact that\nexecPlan pointers are not copied into the EPQ estate's es_param_exec_vals.\nBut it's possible for that assumption to fail, if the initplan is only\nreached conditionally.  For example, a sub-select inside a CASE expression\ncould be reached during a recheck when it had not been previously, if the\nCASE test depends on a column that was just updated.\n\nThis bug is old, appearing to date back to my rewrite of EvalPlanQual in\ncommit 9f2ee8f28, but was not detected until Kyle Samson reported a case.\n\nTo fix, force all not-yet-evaluated initplans used within the EPQ plan\nsubtree to be evaluated at the start of the recheck, before entering the\nEPQ environment.  This could be inefficient, if such an initplan is\nexpensive and goes unused again during the recheck --- but that's piling\none layer of improbability atop another.  It doesn't seem worth adding\nmore complexity to prevent that, at least not in the back branches.\n\nIt was convenient to use the new-in-v11 ExecEvalParamExecParams function\nto implement this, but I didn't like either its name or the specifics of\nits API, so revise that.\n\nBack-patch all the way.  Rather than rewrite the patch to avoid depending\non bms_next_member() in the oldest branches, I chose to back-patch that\nfunction into 9.4 and 9.3.  (This isn't the first time back-patches have\nneeded that, and it exhausted my patience.)  I also chose to back-patch\nsome test cases added by commits 71404af2a and 342a1ffa2 into 9.4 and 9.3,\nso that the 9.x versions of eval-plan-qual.spec are all the same.\n\nAndrew Gierth diagnosed the problem and contributed the added test cases,\nthough the actual code changes are by me.\n\nDiscussion: https://postgr.es/m/A033A40A-B234-4324-BE37-272279F7B627@tripadvisor.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/1f4a920b7309499d2d0c4ceda5e6356e10bc51da"},{"sha":"8f32bacc006692e63f137924d5849b3cb9f2d4d3","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"In v11, disable JIT by default (it's still enabled by default in HEAD).\n\nPer discussion, JIT isn't quite mature enough to ship enabled-by-default.\n\nI failed to resist the temptation to do a bunch of copy-editing on the\nrelated documentation.  Also, clean up some inconsistencies in which\nsection of config.sgml the JIT GUCs are documented in vs. what guc.c\nand postgresql.config.sample had.\n\nDiscussion: https://postgr.es/m/20180914222657.mw25esrzbcnu6qlu@alap3.anarazel.de","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/8f32bacc006692e63f137924d5849b3cb9f2d4d3"},{"sha":"d58c7899bbf6772df43c681ba220daebe61b8382","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 19/1705] Copy function for logical replication slots\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/19/1705\nPatch(es): https://www.postgresql.org/message-id/CAD21AoBxE8ok4a_xnZ=UV0K=O5OF+gu208zGP__=TR9SNFARZA@mail.gmail.com\nAuthor(s): Masahiko Sawada","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/d58c7899bbf6772df43c681ba220daebe61b8382"}]}
{"actor":{"display_login":"postgresql-cfbot"}}