{"push_id":2589785535,"size":39,"distinct_size":39,"ref":"refs/heads/master","head":"0c7e6b791a316431fb206a9ae2184377c4296995","before":"9effb63e0dd12b0704cd8e11106fe08ff5c9d685","commits":[{"sha":"3dacd9bf32873c80045a2b758d64c031d70dac83","author":{"name":"Andrew Dunstan","email":"02e0a999c50b1f88df7a8f5a04e1b76b35ea6a88@dunslane.net"},"message":"Prevent possibly spurious error when running perl -cw","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/3dacd9bf32873c80045a2b758d64c031d70dac83"},{"sha":"a194106c1b4468c74dbf6e83d845be86239844aa","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"MSVC builds must use a separate stamp file for copying generated headers.\n\nCommit bad51a49a tried to use a shortcut with just one stamp file\nrecording the actions of generating the pg_*_d.h headers and copying\nthem to the src/include/catalog/ directory.  That doesn't work in all\nscenarios though, so we must use two stamp files like the Makefiles do.\n\nJohn Naylor\n\nDiscussion: https://postgr.es/m/CANFyU944GdHr=puPbA78STnqr=8kgMrGF-VDHck6aO_-qNDALg@mail.gmail.com","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/a194106c1b4468c74dbf6e83d845be86239844aa"},{"sha":"cfb758b6d9c1df58fb1dfd5d3f6e70393fb17869","author":{"name":"Magnus Hagander","email":"9f4ca770b638615ac5c3e0d2da16b77c80c2f2c6@hagander.net"},"message":"Fix error message on short read of pg_control\n\nInstead of saying \"error: success\", indicate that we got a working read\nbut it was too short.","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/cfb758b6d9c1df58fb1dfd5d3f6e70393fb17869"},{"sha":"7d5b403b8d418742b734f85fda32b0eca8ee4113","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Small improvement for plpgsql regression test.\n\nUse DISCARD PLANS instead of a reconnect to force reconstruction of\na cached plan; this corresponds more nearly to what people might\nactually do in practice.","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/7d5b403b8d418742b734f85fda32b0eca8ee4113"},{"sha":"f586f8638929b54de9e7f6b65fe6916b8cee38fe","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Recognize that MSVC can support strtoll() and strtoull().\n\nThis is needed for full support of \"long long\" variables in ecpg, but\nthe previous patch for bug #15080 (commits 51057feaa et al) missed it.\nIn MSVC versions where the functions don't exist under those names,\nwe can nonetheless use _strtoi64() and _strtoui64().\n\nLike the previous patch, back-patch all the way.\n\nDang Minh Huong\n\nDiscussion: https://postgr.es/m/151935568942.1461.14623890240535309745@wrigleys.postgresql.org","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/f586f8638929b54de9e7f6b65fe6916b8cee38fe"},{"sha":"dbccdd375b41618ca4ee3d1ea7109ab7f95d0865","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Add some test coverage for ecpg's \"long long\" support.\n\nThis will only actually exercise the \"long long\" code paths on platforms\nwhere \"long\" is 32 bits --- otherwise, the SQL bigint type maps to\nplain \"long\", and we will test that code path instead.  But that's\nprobably sufficient coverage, and anyway we weren't testing either\ncode path before.\n\nDang Minh Huong, tweaked a bit by me\n\nDiscussion: https://postgr.es/m/151935568942.1461.14623890240535309745@wrigleys.postgresql.org","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/dbccdd375b41618ca4ee3d1ea7109ab7f95d0865"},{"sha":"b949bbcb7eaf3719b541cbae99ef6c4b031174a1","author":{"name":"Robert Haas","email":"cc4ab156f0be9feefe10b35a552fd319cd7679ae@postgresql.org"},"message":"Further adjust comment in get_partition_dispatch_recurse.\n\nIn editing 09b12d52db1cf1a4c72d876f3fb6c9d06919e51a I made it wrong;\nfix that and try to more clearly explain the situation.\n\nPatch by me, reviewed by David Rowley and Amit Langote\n\nDiscussion: http://postgr.es/m/CA+TgmobAq+mA5hzm0a5OS38qQY5758DDDGqa3sBJN4hvir-H9w@mail.gmail.com","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/b949bbcb7eaf3719b541cbae99ef6c4b031174a1"},{"sha":"5e79405d82992efce15c27694f10fb4e1ac32657","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Hot-fix ecpg regression test for missing ecpg_config.h inclusion.\n\nI don't think this is really the best long-term answer, and in\nparticular it doesn't fix the pre-existing hazard in sqltypes.h.\nBut for the moment let's just try to make the buildfarm green again.\n\nDiscussion: https://postgr.es/m/151935568942.1461.14623890240535309745@wrigleys.postgresql.org","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/5e79405d82992efce15c27694f10fb4e1ac32657"},{"sha":"e2b83ff556deb9a0001bdf6b511f8cfc9189ac10","author":{"name":"Stephen Frost","email":"d3eaa418a359156a10c6383b2e3a44959960ecf6@snowman.net"},"message":"Fix for globals.c- c.h must come first\n\nCommit da9b580 mistakenly put a system header before postgres.h (which\nincludes c.h).  That can cause portability issues and broke (at least)\nbuilds with older Windows compilers.\n\nDiscovered by Mark Dilger.\n\nDiscussion: https://postgr.es/m/BF04A27A-D132-4927-A80A-BAD18695E954@gmail.com","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/e2b83ff556deb9a0001bdf6b511f8cfc9189ac10"},{"sha":"a6228128fc48c222953dfd41fd438522a184054c","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Arrange to supply declarations for strtoll/strtoull if needed.\n\nBuildfarm member dromedary is still unhappy about the recently-added\necpg \"long long\" tests.  The reason turns out to be that it includes\n\"-ansi\" in its CFLAGS, and in their infinite wisdom Apple have decided\nto hide the declarations of strtoll/strtoull in C89-compliant builds.\n(I find it pretty curious that they hide those function declarations\nwhen you can nonetheless declare a \"long long\" variable, but anyway\nthat is their behavior, both on dromedary's obsolete macOS version and\nthe newest and shiniest.)  As a result, gcc assumes these functions\nreturn \"int\", leading naturally to wrong results.\n\n(Looking at dromedary's past build results, it's evident that this\nproblem also breaks pg_strtouint64() on 32-bit platforms; but we\nevidently have no regression tests that exercise that function with\nvalues above 32 bits.)\n\nTo fix, supply declarations for these functions when the platform\nprovides the functions but not the declarations, using the same type\nof mechanism as we use for some other similar cases.\n\nDiscussion: https://postgr.es/m/151935568942.1461.14623890240535309745@wrigleys.postgresql.org","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/a6228128fc48c222953dfd41fd438522a184054c"},{"sha":"06f66cff9e0b93db81db1595156b2aff8ba1786e","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Support platforms where strtoll/strtoull are spelled __strtoll/__strtoull.\n\nAncient HPUX, for one, does this.  We hadn't noticed due to the lack\nof regression tests that required a working strtoll.\n\n(I was slightly tempted to remove the other historical spelling,\nstrto[u]q, since it seems we have no buildfarm members testing that case.\nBut I refrained.)\n\nDiscussion: https://postgr.es/m/151935568942.1461.14623890240535309745@wrigleys.postgresql.org","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/06f66cff9e0b93db81db1595156b2aff8ba1786e"},{"sha":"e7a808f947c66e2e2186c9495359865dadaf511a","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Assorted minor cleanups for bootstrap-data Perl scripts.\n\nFindDefinedSymbol was intended to take an array of possible include\npaths, but it never actually worked correctly for any but the first\narray element.  Since there's no use-case for more than one path\nanyway, let's just simplify this code and its callers by redefining\nit as taking only one include path.\n\nMinor other code-beautification without functional effects, except\nthat in one place we format the output as pgindent would do.\n\nJohn Naylor\n\nDiscussion: https://postgr.es/m/CAJVSVGXM_n32hTTkircW4_K1LQFsJNb6xjs0pAP4QC0ZpyJfPQ@mail.gmail.com","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/e7a808f947c66e2e2186c9495359865dadaf511a"},{"sha":"c6e846446d17db40883eed91fa448e65333a0ae1","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"printf(\"%lf\") is not portable, so omit the \"l\".\n\nThe \"l\" (ell) width spec means something in the corresponding scanf usage,\nbut not here.  While modern POSIX says that applying \"l\" to \"f\" and other\nfloating format specs is a no-op, SUSv2 says it's undefined.  Buildfarm\nexperience says that some old compilers emit warnings about it, and at\nleast one old stdio implementation (mingw's \"ANSI\" option) actually\nproduces wrong answers and/or crashes.\n\nDiscussion: https://postgr.es/m/21670.1526769114@sss.pgh.pa.us\nDiscussion: https://postgr.es/m/c085e1da-0d64-1c15-242d-c921f32e0d5c@dunslane.net","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/c6e846446d17db40883eed91fa448e65333a0ae1"},{"sha":"a13b47a59ffce6f3c13c8b777738a3aab1db10d3","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Fix unportable usage of printf(\"%m\").\n\nWhile glibc's version of printf accepts %m, most others do not;\nto be portable, we have to do it the hard way with strerror(errno).\npg_verify_checksums evidently did not get that memo.\n\nNoted while fooling around with NetBSD-current, which generates\na compiler warning for this mistake.","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/a13b47a59ffce6f3c13c8b777738a3aab1db10d3"},{"sha":"81256cd05f0745353c6572362155b57250a0d2a0","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Fix unsafe usage of strerror(errno) within ereport().\n\nThis is the converse of the unsafe-usage-of-%m problem: the reason\nereport/elog provide that format code is mainly to dodge the hazard\nof errno getting changed before control reaches functions within the\narguments of the macro.  I only found one instance of this hazard,\nbut it's been there since 9.4 :-(.","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/81256cd05f0745353c6572362155b57250a0d2a0"},{"sha":"3ce7f72529f5829f73e18240740bafc939b650b5","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"pg_basebackup: Remove short option -k\n\n-k meant --no-verify-checksums, which is the opposite of what initdb\nuses -k for.  After discussion, a short option does not seem necessary,\nso just keep the long option.\n\nDiscussion: https://www.postgresql.org/message-id/flat/d510f8aa-19e1-d06e-7630-ad27f7441d68%402ndquadrant.com","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/3ce7f72529f5829f73e18240740bafc939b650b5"},{"sha":"3f5e3a98443c7f437465d79e4b99a0a661ae1b9b","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Doc: fix bogus cross-reference link.\n\nAn xref to a <para>'s ID isn't very helpful because paras don't have\nnames.  This causes a warning while building PDFs, though for some\nreason not while building HTML.  The link arguably went to the wrong\nplace, too.\n\nTo fix, introduce a sub-section we can reference.","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/3f5e3a98443c7f437465d79e4b99a0a661ae1b9b"},{"sha":"f755a152d4e3e6f913c6b7b6afe1785b1171c1cb","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Improve spelling of new FINALFUNC_MODIFY aggregate attribute.\n\nI'd used SHARABLE as a value originally, but Peter Eisentraut points out\nthat dictionaries agree that SHAREABLE is the preferred spelling.\nRun around and change that before it's too late.\n\nDiscussion: https://postgr.es/m/d2e1afd4-659c-50d6-1b20-7cfd3675e909@2ndquadrant.com","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/f755a152d4e3e6f913c6b7b6afe1785b1171c1cb"},{"sha":"17485552ec3a7f9a19d568e4bb9b4affae4efdfa","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"doc: Fix some whitespace issues","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/17485552ec3a7f9a19d568e4bb9b4affae4efdfa"},{"sha":"806d08c0489f72282e0a25629e0d6054176e0c9d","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"Update key words table for version 11","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/806d08c0489f72282e0a25629e0d6054176e0c9d"}]}
{"actor":{"display_login":"Algunenano"}}