{"push_id":1994323855,"size":8,"distinct_size":1,"ref":"refs/heads/commitfest/14/1284","head":"8b6f96e65e95c59103b5f75a2b5d6b7ba3ac4b27","before":"1f200073a6d23f1cf92ad55fa713889450806bf8","commits":[{"sha":"4bd1994650fddf49e717e35f1930d62208845974","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Make DatumGetFoo/PG_GETARG_FOO/PG_RETURN_FOO macro names more consistent.\n\nBy project convention, these names should include \"P\" when dealing with a\npointer type; that is, if the result of a GETARG macro is of type FOO *,\nit should be called PG_GETARG_FOO_P not just PG_GETARG_FOO.  Some newer\ntypes such as JSONB and ranges had not followed the convention, and a\nnumber of contrib modules hadn't gotten that memo either.  Rename the\noffending macros to improve consistency.\n\nIn passing, fix a few places that thought PG_DETOAST_DATUM() returns\na Datum; it does not, it returns \"struct varlena *\".  Applying\nDatumGetPointer to that happens not to cause any bad effects today,\nbut it's formally wrong.  Also, adjust an ltree macro that was designed\nwithout any thought for what pgindent would do with it.\n\nThis is all cosmetic and shouldn't have any impact on generated code.\n\nMark Dilger, some further tweaks by me\n\nDiscussion: https://postgr.es/m/EA5676F4-766F-4F38-8348-ECC7DB427C6A@gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/4bd1994650fddf49e717e35f1930d62208845974"},{"sha":"66917bfaa7bb0b6bae52a5fe631a8b6443203f55","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Make ExplainOpenGroup and ExplainCloseGroup public.\n\nExtensions with custom plan nodes might like to use these in their\nEXPLAIN output.\n\nHadi Moshayedi\n\nDiscussion: https://postgr.es/m/CA+_kT_dU-rHCN0u6pjA6bN5CZniMfD=-wVqPY4QLrKUY_uJq5w@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/66917bfaa7bb0b6bae52a5fe631a8b6443203f55"},{"sha":"eb5c404b17752ca566947f12cb702438dcccdcb1","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Minor code-cleanliness improvements for btree.\n\nMake the btree page-flags test macros (P_ISLEAF and friends) return clean\nboolean values, rather than values that might not fit in a bool.  Use them\nin a few places that were randomly referencing the flag bits directly.\n\nIn passing, change access/nbtree/'s only direct use of BUFFER_LOCK_SHARE to\nBT_READ.  (Some think we should go the other way, but as long as we have\nBT_READ/BT_WRITE, let's use them consistently.)\n\nMasahiko Sawada, reviewed by Doug Doole\n\nDiscussion: https://postgr.es/m/CAD21AoBmWPeN=WBB5Jvyz_Nt3rmW1ebUyAnk3ZbJP3RMXALJog@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/eb5c404b17752ca566947f12cb702438dcccdcb1"},{"sha":"ec9e05b3c392ba9587f283507459737684539574","author":{"name":"Andres Freund","email":"c6cbfe878b4ee67646e7630734db67f536518d54@anarazel.de"},"message":"Fix crash restart bug introduced in 8356753c212.\n\nThe bug was caused by not re-reading the control file during crash\nrecovery restarts, which lead to an attempt to pfree() shared memory\ncontents. The fix is to re-read the control file, which seems good\nanyway.\n\nIt's unclear as of this moment, whether we want to keep the\nrefactoring introduced in the commit referenced above, or come up with\nan alternative approach. But fixing the bug in the mean time seems\nlike a good idea regardless.\n\nA followup commit will introduce regression test coverage for crash\nrestarts.\n\nReported-By: Tom Lane\nDiscussion: https://postgr.es/m/14134.1505572349@sss.pgh.pa.us","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/ec9e05b3c392ba9587f283507459737684539574"},{"sha":"a1924a4ea29399111e5155532ca24c9c51d3c82d","author":{"name":"Andres Freund","email":"c6cbfe878b4ee67646e7630734db67f536518d54@anarazel.de"},"message":"Add test for postmaster crash restarts.\n\nGiven that I managed to break this...  We probably should extend the\ntests to also cover other sub-processes dying, but that's something\nfor later.\n\nAuthor: Andres Freund\nDiscussion: https://postgr.es/m/20170917080752.rcmihzfmgbeuqjk2@alap3.anarazel.de","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/a1924a4ea29399111e5155532ca24c9c51d3c82d"},{"sha":"0fb9e4ace5ce4d479d839a720f32b99fdc87f455","author":{"name":"Andres Freund","email":"c6cbfe878b4ee67646e7630734db67f536518d54@anarazel.de"},"message":"Fix uninitialized variable in dshash.c.\n\nA bugfix for commit 8c0d7bafad36434cb08ac2c78e69ae72c194ca20.  The code\nwould have crashed if hashtable->size_log2 ever had the same value as\nhashtable->control->size_log2 by coincidence.\n\nPer Valgrind.\n\nAuthor: Thomas Munro\nReported-By: Tomas Vondra\nDiscussion: https://postgr.es/m/e72fb33c-4f31-f276-e972-263d9b59554d%402ndquadrant.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/0fb9e4ace5ce4d479d839a720f32b99fdc87f455"},{"sha":"f8e5f156b30efee5d0038b03e38735773abcb7ed","author":{"name":"Andres Freund","email":"c6cbfe878b4ee67646e7630734db67f536518d54@anarazel.de"},"message":"Rearm statement_timeout after each executed query.\n\nPreviously statement_timeout, in the extended protocol, affected all\nmessages till a Sync message.  For clients that pipeline/batch query\nexecution that's problematic.\n\nInstead disable timeout after each Execute message, and enable, if\nnecessary, the timer in start_xact_command(). As that's done only for\nExecute and not Parse / Bind, pipelining the latter two could still\ncause undesirable timeouts. But a survey of protocol implementations\nshows that all drivers issue Sync messages when preparing, and adding\ntimeout rearming to both is fairly expensive for the common parse /\nbind / execute sequence.\n\nAuthor: Tatsuo Ishii, editorialized by Andres Freund\nReviewed-By: Takayuki Tsunakawa, Andres Freund\nDiscussion: https://postgr.es/m/20170222.115044.1665674502985097185.t-ishii@sraoss.co.jp","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/f8e5f156b30efee5d0038b03e38735773abcb7ed"},{"sha":"8b6f96e65e95c59103b5f75a2b5d6b7ba3ac4b27","author":{"name":"CommitFest Bot","email":"aab6a594935fe5db0d690bc154b19f642bfbe9d7@cputube.org"},"message":"[CF 14/1284] Controlling toast_tuple_target to tune rows >2kB\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/14/1284\nPatch(es): https://www.postgresql.org/message-id/CANP8%2Bj%2Bvo11fsK5jjuN1N8gsvw_kpbby17AzaXUuzLydW3Yv%2BQ%40mail.gmail.com\nAuthor(s): Simon Riggs","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/8b6f96e65e95c59103b5f75a2b5d6b7ba3ac4b27"}]}
{"actor":{"display_login":"postgresql-cfbot"}}