{"push_id":2423299326,"size":8,"distinct_size":1,"ref":"refs/heads/commitfest/17/1509","head":"a8eb55e661729b511ec28c1d90539eb71e2fe6e4","before":"d34a0b9810700c459c1afe2d01e8b57a36b0a192","commits":[{"sha":"0f0deb71948321efc89cf4e3e8cbd9750cc9e566","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Improve predtest.c's handling of cases with NULL-constant inputs.\n\nCurrently, if operator_predicate_proof() is given an operator clause like\n\"something op NULL\", it just throws up its hands and reports it can't prove\nanything.  But we can often do better than that, if the operator is strict,\nbecause then we know that the clause returns NULL overall.  Depending on\nwhether we're trying to prove or refute something, and whether we need\nweak or strong semantics for NULL, this may be enough to prove the\nimplication, especially when we rely on the standard rule that \"false\nimplies anything\".  In particular, this lets us do something useful with\nquestions like \"does X IN (1,3,5,NULL) imply X <= 5?\"  The null entry\nin the IN list can effectively be ignored for this purpose, but the\nproof rules were not previously smart enough to deduce that.\n\nThis patch is by me, but it owes something to previous work by\nAmit Langote to try to solve problems of the form mentioned.\nThanks also to Emre Hasegeli and Ashutosh Bapat for review.\n\nDiscussion: https://postgr.es/m/3bad48fc-f257-c445-feeb-8a2b2fb622ba@lab.ntt.co.jp","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/0f0deb71948321efc89cf4e3e8cbd9750cc9e566"},{"sha":"742869946f4ff121778c2e5923ab51a451b16497","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Fix mishandling of quoted-list GUC values in pg_dump and ruleutils.c.\n\nCode that prints out the contents of setconfig or proconfig arrays in\nSQL format needs to handle GUC_LIST_QUOTE variables differently from\nother ones, because for those variables, flatten_set_variable_args()\nalready applied a layer of quoting.  The value can therefore safely\nbe printed as-is, and indeed must be, or flatten_set_variable_args()\nwill muck it up completely on reload.  For all other GUC variables,\nit's necessary and sufficient to quote the value as a SQL literal.\n\nWe'd recognized the need for this long ago, but mis-analyzed the\nneed slightly, thinking that all GUC_LIST_INPUT variables needed\nthe special treatment.  That's actually wrong, since a valid value\nof a LIST variable might include characters that need quoting,\nalthough no existing variables accept such values.\n\nMore to the point, we hadn't made any particular effort to keep the\nvarious places that deal with this up-to-date with the set of variables\nthat actually need special treatment, meaning that we'd do the wrong\nthing with, for example, temp_tablespaces values.  This affects dumping\nof SET clauses attached to functions, as well as ALTER DATABASE/ROLE SET\ncommands.\n\nIn ruleutils.c we can fix it reasonably honestly by exporting a guc.c\nfunction that allows discovering the flags for a given GUC variable.\nBut pg_dump doesn't have easy access to that, so continue the old method\nof having a hard-wired list of affected variable names.  At least we can\nfix it to have just one list not two, and update the list to match\ncurrent reality.\n\nA remaining problem with this is that it only works for built-in\nGUC variables.  pg_dump's list obvious knows nothing of third-party\nextensions, and even the \"ask guc.c\" method isn't bulletproof since\nthe relevant extension might not be loaded.  There's no obvious\nsolution to that, so for now, we'll just have to discourage extension\nauthors from inventing custom GUCs that need GUC_LIST_QUOTE.\n\nThis has been busted for a long time, so back-patch to all supported\nbranches.\n\nMichael Paquier and Tom Lane, reviewed by Kyotaro Horiguchi and\nPavel Stehule\n\nDiscussion: https://postgr.es/m/20180111064900.GA51030@paquier.xyz","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/742869946f4ff121778c2e5923ab51a451b16497"},{"sha":"846b5a525746b83813771ec4720d664408c47c43","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Prevent extensions from creating custom GUCs that are GUC_LIST_QUOTE.\n\nPending some solution for the problems noted in commit 742869946,\ndisallow dynamic creation of GUC_LIST_QUOTE variables.\n\nIf there are any extensions out there using this feature, they'd not\nbe happy for us to start enforcing this rule in minor releases, so\nthis is a HEAD-only change.  The previous commit didn't make things\nany worse than they already were for such cases.\n\nDiscussion: https://postgr.es/m/20180111064900.GA51030@paquier.xyz","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/846b5a525746b83813771ec4720d664408c47c43"},{"sha":"a02671cfdeac3bb86ebf8f8577faf69730c4f80e","author":{"name":"Andres Freund","email":"c6cbfe878b4ee67646e7630734db67f536518d54@anarazel.de"},"message":"Empty CXXFLAGS inherited from autoconf.\n\nWe do the same for CFLAGS.  This was an omission in 6869b4f25.\n\nReported-By: Catalin Iacob","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/a02671cfdeac3bb86ebf8f8577faf69730c4f80e"},{"sha":"4317cc68a284f041abc583ced4ef7ede2f73fb51","author":{"name":"Andres Freund","email":"c6cbfe878b4ee67646e7630734db67f536518d54@anarazel.de"},"message":"Fix typo in BITCODE_CXXFLAGS assignment.\n\nTypoed-In: 5b2526c83832e\nReported-By: Catalin Iacob","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/4317cc68a284f041abc583ced4ef7ede2f73fb51"},{"sha":"432bb9e04da4d4a1799b1fe7c723b975cb070c43","author":{"name":"Andres Freund","email":"c6cbfe878b4ee67646e7630734db67f536518d54@anarazel.de"},"message":"Basic JIT provider and error handling infrastructure.\n\nThis commit introduces:\n\n1) JIT provider abstraction, which allows JIT functionality to be\n   implemented in separate shared libraries. That's desirable because\n   it allows to install JIT support as a separate package, and because\n   it allows experimentation with different forms of JITing.\n2) JITContexts which can be, using functions introduced in follow up\n   commits, used to emit JITed functions, and have them be cleaned up\n   on error.\n3) The outline of a LLVM JIT provider, which will be fleshed out in\n   subsequent commits.\n\nDocumentation for GUCs added, and for JIT in general, will be added in\nlater commits.\n\nAuthor: Andres Freund, with architectural input from Jeff Davis\nDiscussion: https://postgr.es/m/20170901064131.tazjxwus3k2w3ybh@alap3.anarazel.de","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/432bb9e04da4d4a1799b1fe7c723b975cb070c43"},{"sha":"31bc604e0b74805ff9e84a2d549ca82be665d0a6","author":{"name":"Andres Freund","email":"c6cbfe878b4ee67646e7630734db67f536518d54@anarazel.de"},"message":"Add file containing extensions of the LLVM C API.\n\nAuthor: Andres Freund\nDiscussion: https://postgr.es/m/20170901064131.tazjxwus3k2w3ybh@alap3.anarazel.de","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/31bc604e0b74805ff9e84a2d549ca82be665d0a6"},{"sha":"a8eb55e661729b511ec28c1d90539eb71e2fe6e4","author":{"name":"Commitfest Bot","email":"aab6a594935fe5db0d690bc154b19f642bfbe9d7@cputube.org"},"message":"[CF 17/1509] PQhost undefined behavior with both host and hostaddr types in connection string\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/1509\nPatch(es): https://www.postgresql.org/message-id/20180316.130314.19595957.horiguchi.kyotaro%40lab.ntt.co.jp\nAuthor(s): Haribabu Kommi","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/a8eb55e661729b511ec28c1d90539eb71e2fe6e4"}]}
{"actor":{"display_login":"postgresql-cfbot"}}