{"push_id":3107660786,"size":1000,"distinct_size":153,"ref":"refs/heads/master","head":"037e6914ad3e18235a43418d7a778d51be774a8d","before":"016c9908347ed2ba7b9d7101c858ea7730b6c0b0","commits":[{"sha":"f248453b7a1b0590b3c7cf32a958573b70e23b09","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Update sepgsql regression test output for getObjectDescription() changes.\n\nMissed in commit b86b7bfa3.  Per buildfarm.","distinct":false,"url":"https://api.github.com/repos/postgrespro/sqljson/commits/f248453b7a1b0590b3c7cf32a958573b70e23b09"},{"sha":"2eb809ad7e71737b1a1ef5679d8e4c88e785669e","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Update non-default collation tests for getObjectDescription() changes.\n\nSigh, also missed in commit b86b7bfa3.  Per buildfarm.","distinct":false,"url":"https://api.github.com/repos/postgrespro/sqljson/commits/2eb809ad7e71737b1a1ef5679d8e4c88e785669e"},{"sha":"7019c21c1bf51eafb56595b916c216ca860ad499","author":{"name":"Magnus Hagander","email":"9f4ca770b638615ac5c3e0d2da16b77c80c2f2c6@hagander.net"},"message":"Remove incorrect statement about IPC configuration on OpenBSD\n\nkern.ipc.shm_use_phys is not a sysctl on OpenBSD, and SEMMAP is not\na kernel configuration option. These were probably copy pasteos from\nwhen the documentation had a single paragraph for *BSD.\n\nAuthor: Daniel Gustafsson <daniel@yesql.se>","distinct":false,"url":"https://api.github.com/repos/postgrespro/sqljson/commits/7019c21c1bf51eafb56595b916c216ca860ad499"},{"sha":"9a8aa25ccc6c285cd4f02afe4718eafd20dc34c5","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Fix misidentification of SQL statement type in plpgsql's exec_stmt_execsql.\n\nTo distinguish SQL statements that are INSERT/UPDATE/DELETE from other\nones, exec_stmt_execsql looked at the post-rewrite form of the statement\nrather than the original.  This is problematic because it did that only\nduring first execution of the statement (in a session), but the correct\nanswer could change later due to addition or removal of DO INSTEAD rules\nduring the session.  That could lead to an Assert failure, as reported\nby Tushar Ahuja and Robert Haas.  In non-assert builds, there's a hazard\nthat we would fail to enforce STRICT behavior when we'd be expected to.\nThat would happen if an initially present DO INSTEAD, that replaced the\noriginal statement with one of a different type, were removed; after that\nthe statement should act \"normally\", including strictness enforcement, but\nit didn't.  (The converse case of enforcing strictness when we shouldn't\ndoesn't seem to be a hazard, as addition of a DO INSTEAD that changes the\nstatement type would always lead to acting as though the statement returned\nzero rows, so that the strictness error could not fire.)\n\nTo fix, inspect the original form of the statement not the post-rewrite\nform, making it valid to assume the answer can't change intra-session.\nThis should lead to the same answer in every case except when there is a\nDO INSTEAD that changes the statement type; we will now set mod_stmt=true\nanyway, while we would not have done so before.  That breaks the Assert\nin the SPI_OK_REWRITTEN code path, which expected the latter behavior.\nIt might be all right to assert mod_stmt rather than !mod_stmt there,\nbut I'm not entirely convinced that that'd always hold, so just remove\nthe assertion altogether.\n\nThis has been broken for a long time, so back-patch to all supported\nbranches.\n\nDiscussion: https://postgr.es/m/CA+TgmoZUrRN4xvZe_BbBn_Xp0BDwuMEue-0OyF0fJpfvU2Yc7Q@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgrespro/sqljson/commits/9a8aa25ccc6c285cd4f02afe4718eafd20dc34c5"},{"sha":"71b349aef4c4eb766e556360cfb5f5190c02b9c1","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Update a couple of long-obsolete comments in pg_type.h.","distinct":false,"url":"https://api.github.com/repos/postgrespro/sqljson/commits/71b349aef4c4eb766e556360cfb5f5190c02b9c1"},{"sha":"8a56ff484808e9c05df9656cf4244229e8c7960d","author":{"name":"Andrew Dunstan","email":"02e0a999c50b1f88df7a8f5a04e1b76b35ea6a88@dunslane.net"},"message":"Don't force a blank line before comments in perl code\n\nSuggestion from Bruce Momjian\n\nDiscussion: https://postgr.es/m/20180525190445.GA2213@momjian.us","distinct":false,"url":"https://api.github.com/repos/postgrespro/sqljson/commits/8a56ff484808e9c05df9656cf4244229e8c7960d"},{"sha":"3a7cc727c7c502353dbb730a0db793abec4de44b","author":{"name":"Andrew Dunstan","email":"02e0a999c50b1f88df7a8f5a04e1b76b35ea6a88@dunslane.net"},"message":"Don't fall off the end of perl functions\n\nThis complies with the perlcritic policy\nSubroutines::RequireFinalReturn, which is a severity 4 policy. Since we\nonly currently check at severity level 5, the policy is raised to that\nlevel until we move to level 4 or lower, so that any new infringements\nwill be caught.\n\nA small cosmetic piece of tidying of the pgperlcritic script is\nincluded.\n\nMike Blackwell\n\nDiscussion: https://postgr.es/m/CAESHdJpfFm_9wQnQ3koY3c91FoRQsO-fh02za9R3OEMndOn84A@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgrespro/sqljson/commits/3a7cc727c7c502353dbb730a0db793abec4de44b"},{"sha":"f963f80970641246cbba172e197068193ad65189","author":{"name":"Andrew Dunstan","email":"02e0a999c50b1f88df7a8f5a04e1b76b35ea6a88@dunslane.net"},"message":"Avoid use of unportable hex constant in convutils.pm\n\nDiscussion: https://postgr.es/m/5a6d6de8-cff8-1ffb-946c-ccf381800ea1@2ndQuadrant.com","distinct":false,"url":"https://api.github.com/repos/postgrespro/sqljson/commits/f963f80970641246cbba172e197068193ad65189"},{"sha":"99164e6952917009929026a9a11e4a500f599c40","author":{"name":"Bruce Momjian","email":"9ae9c44b775ee9b29f4f502415e02e61a9b1a6a0@momjian.us"},"message":"doc:  adjust DECLARE docs to mention FOR UPDATE behavior\n\nReported-by: Peter Eisentraut\n\nDiscussion: https://postgr.es/m/8dc63ba7-dc56-fc7c-fc16-4fae03e3bfe6@2ndquadrant.com\n\nAuthor: Peter Eisentraut, Tom Lane, me\n\nBackpatch-through: 9.3","distinct":false,"url":"https://api.github.com/repos/postgrespro/sqljson/commits/99164e6952917009929026a9a11e4a500f599c40"},{"sha":"6a75b58065c8da69a259657fc40d18e76157f265","author":{"name":"Bruce Momjian","email":"9ae9c44b775ee9b29f4f502415e02e61a9b1a6a0@momjian.us"},"message":"doc:  mark 'replaceable' parameter for backup program listing\n\nReported-by: Liudmila Mantrova\n\nDiscussion: https://postgr.es/m/f3e2c0f5-5266-d626-58d7-b77e1b29d870@postgrespro.ru\n\nAuthor: Liudmila Mantrova\n\nBackpatch-through: 9.3","distinct":false,"url":"https://api.github.com/repos/postgrespro/sqljson/commits/6a75b58065c8da69a259657fc40d18e76157f265"},{"sha":"01deec5f8ae64b5120cc8c93d54fe0e19e477b02","author":{"name":"Andrew Dunstan","email":"02e0a999c50b1f88df7a8f5a04e1b76b35ea6a88@dunslane.net"},"message":"Return a value from Install.pm's lcopy function\n\nCommit 3a7cc727c was a little over eager about adding an explicit return\nto this function, whose value is checked in most call sites. This change\nreverses that and returns the expected value explicitly. It also adds a\ncheck to the one call site lacking one.","distinct":false,"url":"https://api.github.com/repos/postgrespro/sqljson/commits/01deec5f8ae64b5120cc8c93d54fe0e19e477b02"},{"sha":"3c9cf069454d80b0b4a54a0a90941a88a97b1122","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"Initialize new jsonb iterator to zero\n\nUse palloc0() instead of palloc() to create a new JsonbIterator.\nOtherwise, the isScalar field is sometimes not initialized.  There is\nprobably no impact in practice, but it's cleaner this way and it avoids\nfuture problems.","distinct":false,"url":"https://api.github.com/repos/postgrespro/sqljson/commits/3c9cf069454d80b0b4a54a0a90941a88a97b1122"},{"sha":"08186dc05b3eed9c1f29b3349b122487d84ef3eb","author":{"name":"Teodor Sigaev","email":"231337598724646720571a00c656f975fff6a8f2@sigaev.ru"},"message":"Move _bt_upgrademetapage() into critical section.\n\nAny changes on page should be done in critical section, so move\n_bt_upgrademetapage into critical section. Improve comment. Found by Amit\nKapila during post-commit review of 857f9c36.\n\nAuthor: Amit Kapila","distinct":false,"url":"https://api.github.com/repos/postgrespro/sqljson/commits/08186dc05b3eed9c1f29b3349b122487d84ef3eb"},{"sha":"d3b10f0d64e90e9c78b8adc24ab3e38b30ef60bd","author":{"name":"Alvaro Herrera","email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org"},"message":"Fix grammar\n\nReported-by: Pavlo Golub\nAuthor: Michaël Paquier\nDiscussion: https://postgr.es/m/152741547.20180530101229@cybertec.at","distinct":false,"url":"https://api.github.com/repos/postgrespro/sqljson/commits/d3b10f0d64e90e9c78b8adc24ab3e38b30ef60bd"},{"sha":"0039049fb1d76afef05d550823b27731ad7d7b3d","author":{"name":"Andrew Dunstan","email":"02e0a999c50b1f88df7a8f5a04e1b76b35ea6a88@dunslane.net"},"message":"Fix compile-time warnings on all perl code\n\nThis patch does two things. First, it silences a number of compile-time\nwarnings in the msvc tools files, mainly those due to the fact that in\nsome cases we have more than one package per file. Second it supplies a\ndummy Perl library with just enough of the Windows API referred to in\nour code to let it run these checks cleanly, even on Unix machines where\nthe code is never supposed to run. The dummy library should only be used\nfor that purpose, as its README notes.","distinct":false,"url":"https://api.github.com/repos/postgrespro/sqljson/commits/0039049fb1d76afef05d550823b27731ad7d7b3d"},{"sha":"ef3109500030030b0e8d3c1d7f2b409d702cc49a","author":{"name":"Noah Misch","email":"1db01d43e08596f43a65fb393d969b98ee5b4dc6@leadboat.com"},"message":"Reconcile nodes/*funcs.c with PostgreSQL 11 work.\n\nThis covers new fields in two outfuncs.c functions having no readfuncs.c\ncounterpart.  Thus, this changes only debugging output.","distinct":false,"url":"https://api.github.com/repos/postgrespro/sqljson/commits/ef3109500030030b0e8d3c1d7f2b409d702cc49a"},{"sha":"12b9affb32a636777062b3feb5816621363fc108","author":{"name":"Alvaro Herrera","email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org"},"message":"Tweak partitioning documentation wording\n\nFor clarity, precision, grammar.\n\nAuthor: Justin Pryzby\nReviewed-by: Amit Langote, Álvaro Herrera\nDiscussion: https://postgr.es/m/20180523213513.GM30060@telsasoft.com","distinct":false,"url":"https://api.github.com/repos/postgrespro/sqljson/commits/12b9affb32a636777062b3feb5816621363fc108"},{"sha":"4d6a854f176dbb48e62f017d8234f4736cb48d24","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"Put new command-line options into alphabetical order","distinct":false,"url":"https://api.github.com/repos/postgrespro/sqljson/commits/4d6a854f176dbb48e62f017d8234f4736cb48d24"},{"sha":"2241ad1556b3734b4867117bee8d78ef9577fceb","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"Fix typo","distinct":false,"url":"https://api.github.com/repos/postgrespro/sqljson/commits/2241ad1556b3734b4867117bee8d78ef9577fceb"},{"sha":"3f85c62d9e825eedd1315d249ef1ad793ca78ed4","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"Fix spurious non-ASCII bytes","distinct":false,"url":"https://api.github.com/repos/postgrespro/sqljson/commits/3f85c62d9e825eedd1315d249ef1ad793ca78ed4"}]}
{"actor":{"display_login":"glukhovn"}}