{"push_id":3027057364,"size":23,"distinct_size":1,"ref":"refs/heads/commitfest/20/1704","head":"977c31ec01fbc596e93759de3e9789a7f7dd6d40","before":"ca97c9d79eee1c13d2694580fcc62249738092ad","commits":[{"sha":"15c7293477a6de03234f58898da7fb29f3ab5b94","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Fix bugs in plpgsql's handling of CALL argument lists.\n\nexec_stmt_call() tried to extract information out of a CALL statement's\nargument list without using expand_function_arguments(), apparently in\nthe hope of saving a few nanoseconds by not processing defaulted\narguments.  It got that quite wrong though, leading to crashes with\nnamed arguments, as well as failure to enforce writability of the\nargument for a defaulted INOUT parameter.  Fix and simplify the logic\nby using expand_function_arguments() before examining the list.\n\nAlso, move the argument-examination to just after producing the CALL\ncommand's plan, before invoking the called procedure.  This ensures\nthat we'll track possible changes in the procedure's argument list\ncorrectly, and avoids a hazard of the plan cache being flushed while\nthe procedure executes.\n\nAlso fix assorted falsehoods and omissions in associated documentation.\n\nPer bug #15477 from Alexey Stepanov.\n\nPatch by me, with some help from Pavel Stehule.  Back-patch to v11.\n\nDiscussion: https://postgr.es/m/15477-86075b1d1d319e0a@postgresql.org\nDiscussion: https://postgr.es/m/CAFj8pRA6UsujpTs9Sdwmk-R6yQykPx46wgjj+YZ7zxm4onrDyw@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/15c7293477a6de03234f58898da7fb29f3ab5b94"},{"sha":"9b6fb9fbb48dda828dcca47adc418632ddb36202","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Fix ExecuteCallStmt to not scribble on the passed-in parse tree.\n\nModifying the parse tree at execution time is, or at least ought to be,\nverboten.  It seems quite difficult to actually cause a crash this way\nin v11 (although you can exhibit it pretty easily in HEAD by messing\nwith plan_cache_mode).  Nonetheless, it's risky, so fix and back-patch.\n\nDiscussion: https://postgr.es/m/13789.1541359611@sss.pgh.pa.us","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/9b6fb9fbb48dda828dcca47adc418632ddb36202"},{"sha":"fa534b411c86d2e7441852282ea9f1a491a090a6","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/fa534b411c86d2e7441852282ea9f1a491a090a6"},{"sha":"4bc772e2afa55f26734ff3fbdf27601db030b7e5","author":{"name":"Michael Paquier","email":"17b9e1c64588c7fa6419b4d29dc1f4426279ba01@paquier.xyz"},"message":"Ignore partitioned tables when processing ON COMMIT DELETE ROWS\n\nThose tables have no physical storage, making this option unusable with\npartition trees as at commit time an actual truncation was attempted.\nThere are still issues with the way ON COMMIT actions are done when\nmixing several action types, however this impacts as well inheritance\ntrees, so this issue will be dealt with later.\n\nReported-by: Rajkumar Raghuwanshi\nAuthor: Amit Langote\nReviewed-by: Michael Paquier, Tom Lane\nDiscussion: https://postgr.es/m/CAKcux6mhgcjSiB_egqEAEFgX462QZtncU8QCAJ2HZwM-wWGVew@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/4bc772e2afa55f26734ff3fbdf27601db030b7e5"},{"sha":"dc3e436b191a8f8d6f35fad952dd3dc314ccabf9","author":{"name":"Michael Paquier","email":"17b9e1c64588c7fa6419b4d29dc1f4426279ba01@paquier.xyz"},"message":"Block creation of partitions with open references to its parent\n\nWhen a partition is created as part of a trigger processing, it is\npossible that the partition which just gets created changes the\nproperties of the table the executor of the ongoing command relies on,\ncausing a subsequent crash.  This has been found possible when for\nexample using a BEFORE INSERT which creates a new partition for a\npartitioned table being inserted to.\n\nAny attempt to do so is blocked when working on a partition, with\nregression tests added for both CREATE TABLE PARTITION OF and ALTER\nTABLE ATTACH PARTITION.\n\nReported-by: Dmitry Shalashov\nAuthor: Amit Langote\nReviewed-by: Michael Paquier, Tom Lane\nDiscussion: https://postgr.es/m/15437-3fe01ee66bd1bae1@postgresql.org\nBackpatch-through: 10","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/dc3e436b191a8f8d6f35fad952dd3dc314ccabf9"},{"sha":"1eaeb02a30b307bad4d6a9cc2d596273a5a38a7a","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Last-minute updates for release notes.\n\nSecurity: CVE-2018-16850","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/1eaeb02a30b307bad4d6a9cc2d596273a5a38a7a"},{"sha":"55f3d1029676ad53621716fd15faed5848c9f4cd","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Remove unreferenced pg_opfamily entry.\n\nThe entry with OID 4035, for GIST jsonb_ops, is unused; apparently\nit was added in preparation for index support that never materialized.\nRemove it, and add a regression test case to detect future mistakes\nof the same kind.\n\nDiscussion: https://postgr.es/m/17188.1541379745@sss.pgh.pa.us","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/55f3d1029676ad53621716fd15faed5848c9f4cd"},{"sha":"a3fb382e9c166e398763e3bbf706b6c92a647fe1","author":{"name":"Andres Freund","email":"883768b6dd2c42aea0031b24be8a2da40fef4b64@anarazel.de"},"message":"Fix copy-paste error in errhint() introduced in 691d79a07933.\n\nReported-By: Petr Jelinek\nDiscussion: https://postgr.es/m/c95a620b-34f0-7930-aeb5-f7ab804f26cb@2ndquadrant.com\nBackpatch: 9.4-, like the previous commit","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/a3fb382e9c166e398763e3bbf706b6c92a647fe1"},{"sha":"b0a1ff8a6a01163f830490e6c542ff852d240690","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Last-minute updates for release notes.\n\nI removed the item about the pg_stat_statements change from\nrelease-11.sgml, as part of a sweep to delete items already committed\nin 11.0; but actually we'd best keep it to ensure that people who've\npg_upgraded their databases will take the requisite action.  Also make\nsaid action more visible by making it into its own para.  Noted by\nJonathan Katz.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/b0a1ff8a6a01163f830490e6c542ff852d240690"},{"sha":"3c60d0fa231f7699af5dd83345919d0423305973","author":{"name":"Thomas Munro","email":"1ff054ef0838bf068a4b7c40eef026e560a37025@postgresql.org"},"message":"Remove dsm_resize() and dsm_remap().\n\nThese interfaces were never used in core, didn't handle failure of\nposix_fallocate() correctly and weren't supported on all platforms.\nWe agreed to remove them in 12.\n\nAuthor: Thomas Munro\nReported-by: Andres Freund\nDiscussion: https://postgr.es/m/CAA4eK1%2B%3DyAFUvpFoHXFi_gm8YqmXN-TtkFH%2BVYjvDLS6-SFq-Q%40mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/3c60d0fa231f7699af5dd83345919d0423305973"},{"sha":"8f045e242b2308473f5de532590454294e3d5683","author":{"name":"Michael Paquier","email":"17b9e1c64588c7fa6419b4d29dc1f4426279ba01@paquier.xyz"},"message":"Switch pg_promote to be parallel-safe\n\npg_promote uses nothing relying on a global state, so it is fine to mark\nit as parallel-safe, conclusion based on a detailed analysis from Robert\nHaas.  This also fixes an inconsistency where pg_proc.dat missed to mark\nthe function with its previous value for proparallel, update which does\nnot matter now as the default is used.\n\nBased on a discussion between multiple folks: Laurenz Albe, Robert Haas,\nAmit Kapila, Tom Lane and myself.\n\nDiscussion: https://postgr.es/m/20181029082530.GL14242@paquier.xyz","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/8f045e242b2308473f5de532590454294e3d5683"},{"sha":"add9182e59084faf57bb264fefcd39fbc93fb116","author":{"name":"Michael Paquier","email":"17b9e1c64588c7fa6419b4d29dc1f4426279ba01@paquier.xyz"},"message":"Reorganize format options of psql in alphabetical order\n\nThis makes the addition of new formats easier, and documentation lookups\neasier.\n\nAuthor: Daniel Vérité\nReviewed-by: Fabien Coelho\nDiscussion: https://postgr.es/m/alpine.DEB.2.20.1803081004241.2916@lancre","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/add9182e59084faf57bb264fefcd39fbc93fb116"},{"sha":"9e12fb02b7ec27ff3707a0a7c31f2421ba62c9df","author":{"name":"Thomas Munro","email":"1ff054ef0838bf068a4b7c40eef026e560a37025@postgresql.org"},"message":"Remove some remaining traces of dsm_resize().\n\nA couple of obsolete comments and unreachable blocks remained after\ncommit 3c60d0fa.\n\nDiscussion: https://postgr.es/m/CAA4eK1%2B%3DyAFUvpFoHXFi_gm8YqmXN-TtkFH%2BVYjvDLS6-SFq-Q%40mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/9e12fb02b7ec27ff3707a0a7c31f2421ba62c9df"},{"sha":"8f623bedfb4fee5a125b25720e5451379cf26ff9","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Remove useless symbol from Makefile.global.\n\nI added HAVE_IPV6 to Makefile.global way back in commit 7703e55c3\nso that we could transmit its value to the shell-script version of\ninitdb.  Since initdb was rewritten in C, it's been finding that\nout from pg_config.h instead, so this is useless.  Keeping it here\njust wastes configure and make cycles, plus it's a potential\ntwo-sources-of-truth problem.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/8f623bedfb4fee5a125b25720e5451379cf26ff9"},{"sha":"003c68a3b45d0d135b874acfe04cf3fb79a6f172","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Rename rbtree.c functions to use \"rbt\" prefix not \"rb\" prefix.\n\nThe \"rb\" prefix is used by Ruby, so that our existing code results\nin name collisions that break plruby.  We discussed ways to prevent\nthat by adjusting dynamic linker options, but it seems that at best\nwe'd move the pain to other cases.  Renaming to avoid the collision\nis the only portable fix anyway.  Fortunately, our rbtree code is\nnot (yet?) widely used --- in core, there's only a single usage\nin GIN --- so it seems likely that we can get away with a rename.\n\nI chose to do this basically as s/rb/rbt/g, except for places where\nthere already was a \"t\" after \"rb\".  The patch could have been made\nsmaller by only touching linker-visible symbols, but it would have\nresulted in oddly inconsistent-looking code.  Better to make it look\nlike \"rbt\" was the plan all along.\n\nBack-patch to v10.  The rbtree.c code exists back to 9.5, but\nrb_iterate() which is the actual immediate source of pain was added\nin v10, so it seems like changing the names before that would have\nmore risk than benefit.\n\nPer report from Pavel Raiskup.\n\nDiscussion: https://postgr.es/m/4738198.8KVIIDhgEB@nb.usersys.redhat.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/003c68a3b45d0d135b874acfe04cf3fb79a6f172"},{"sha":"b43df566b372650a9b9e2a0dd9e695c1f16da14f","author":{"name":"Bruce Momjian","email":"9ae9c44b775ee9b29f4f502415e02e61a9b1a6a0@momjian.us"},"message":"GUC: adjust effective_cache_size SQL descriptions\n\nFollow on patch for commit 3e0f1a4741f564c1a2fa6e944729d6967355d8c7.\n\nReported-by: Peter Eisentraut\n\nDiscussion: https://postgr.es/m/369ec766-b947-51bd-4dad-6fb9e026439f@2ndquadrant.com\n\nBackpatch-through: 9.4","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/b43df566b372650a9b9e2a0dd9e695c1f16da14f"},{"sha":"3fd2a7932ef0708dda57369bb20c0499d905cc82","author":{"name":"Thomas Munro","email":"1ff054ef0838bf068a4b7c40eef026e560a37025@postgresql.org"},"message":"Provide pg_pread() and pg_pwrite() for random I/O.\n\nForward to POSIX pread() and pwrite(), or emulate them if unavailable.\nThe emulation is not perfect as the file position is changed, so\nwe'll put pg_ prefixes on the names to minimize the risk of confusion\nin future patches that might inadvertently try to mix pread() and read()\non the same file descriptor.\n\nAuthor: Thomas Munro\nReviewed-by: Tom Lane, Jesper Pedersen\nDiscussion: https://postgr.es/m/CAEepm=02rapCpPR3ZGF2vW=SBHSdFYO_bz_f-wwWJonmA3APgw@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/3fd2a7932ef0708dda57369bb20c0499d905cc82"},{"sha":"c24dcd0cfd949bdf245814c4c2b3df828ee7db36","author":{"name":"Thomas Munro","email":"1ff054ef0838bf068a4b7c40eef026e560a37025@postgresql.org"},"message":"Use pg_pread() and pg_pwrite() for data files and WAL.\n\nCut down on system calls by doing random I/O using offset-based OS\nroutines where available.  Remove the code for tracking the 'virtual'\nseek position.  The only reason left to call FileSeek() was to get\nthe file's size, so provide a new function FileSize() instead.\n\nAuthor: Oskari Saarenmaa, Thomas Munro\nReviewed-by: Thomas Munro, Jesper Pedersen, Tom Lane, Alvaro Herrera\nDiscussion: https://postgr.es/m/CAEepm=02rapCpPR3ZGF2vW=SBHSdFYO_bz_f-wwWJonmA3APgw@mail.gmail.com\nDiscussion: https://postgr.es/m/b8748d39-0b19-0514-a1b9-4e5a28e6a208%40gmail.com\nDiscussion: https://postgr.es/m/a86bd200-ebbe-d829-e3ca-0c4474b2fcb7%40ohmu.fi","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/c24dcd0cfd949bdf245814c4c2b3df828ee7db36"},{"sha":"5613da4cc7910f4b686b818dd1ee68703d62192f","author":{"name":"Andrew Gierth","email":"f5e6496b0ff21826a604b558aceee3773835e92d@postgresql.org"},"message":"Optimize nested ConvertRowtypeExpr nodes.\n\nA ConvertRowtypeExpr is used to translate a whole-row reference of a\nchild to that of a parent. The planner produces nested\nConvertRowtypeExpr while translating whole-row reference of a leaf\npartition in a multi-level partition hierarchy. Executor then\ntranslates the whole-row reference from the leaf partition into all\nthe intermediate parent's whole-row references before arriving at the\nfinal whole-row reference. It could instead translate the whole-row\nreference from the leaf partition directly to the top-most parent's\nwhole-row reference skipping any intermediate translations.\n\nAshutosh Bapat, with tests by Kyotaro Horiguchi and some\neditorialization by me. Reviewed by Andres Freund, Pavel Stehule,\nKyotaro Horiguchi, Dmitry Dolgov, Tom Lane.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/5613da4cc7910f4b686b818dd1ee68703d62192f"},{"sha":"c4f0876fb8d8f84fc0a6fb6aee91de120718664c","author":{"name":"Thomas Munro","email":"1ff054ef0838bf068a4b7c40eef026e560a37025@postgresql.org"},"message":"Remove set-but-unused variable.\n\nClean-up for commit c24dcd0c.\n\nReported-by: Andrew Dunstan\nDiscussion: https://postgr.es/m/2d52ff4a-5440-f6f1-7806-423b0e6370cb%402ndQuadrant.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/c4f0876fb8d8f84fc0a6fb6aee91de120718664c"}]}
{"actor":{"display_login":"postgresql-cfbot"}}