{"push_id":1006188670,"size":51,"distinct_size":7,"ref":"refs/heads/dev/failover-slots","head":"ea0d5d859d0604a3a6394ce21ba24f4222fb2780","before":"31623536c9e5aaef955a06068663eddfe0220cad","commits":[{"sha":"907e4dd2b104bdcb4af042065a92fcd73d5790ec","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Avoid multiple free_struct_lconv() calls on same data.\n\nA failure partway through PGLC_localeconv() led to a situation where\nthe next call would call free_struct_lconv() a second time, leading\nto free() on already-freed strings, typically leading to a core dump.\nAdd a flag to remember whether we need to do that.\n\nPer report from Thom Brown.  His example case only provokes the failure\nas far back as 9.4, but nonetheless this code is obviously broken, so\nback-patch to all supported branches.","distinct":false,"url":"https://api.github.com/repos/2ndQuadrant/postgres/commits/907e4dd2b104bdcb4af042065a92fcd73d5790ec"},{"sha":"41fedc24626696fdf55d0c43131d91757dbe1c66","author":{"email":"79f727108221a92d157723334215101df270f796@gmail.com","name":"Dean Rasheed"},"message":"Fix incorrect varlevelsup in security_barrier_replace_vars().\n\nWhen converting an RTE with securityQuals into a security barrier\nsubquery RTE, ensure that the Vars in the new subquery's targetlist\nall have varlevelsup = 0 so that they correctly refer to the\nunderlying base relation being wrapped.\n\nThe original code was creating new Vars by copying them from existing\nVars referencing the base relation found elsewhere in the query, but\nfailed to account for the fact that such Vars could come from sublink\nsubqueries, and hence have varlevelsup > 0. In practice it looks like\nthis could only happen with nested security barrier views, where the\nouter view has a WHERE clause containing a correlated subquery, due to\nthe order in which the Vars are processed.\n\nBug: #13988\nReported-by: Adam Guthrie\nBackpatch-to: 9.4, where updatable SB views were introduced","distinct":false,"url":"https://api.github.com/repos/2ndQuadrant/postgres/commits/41fedc24626696fdf55d0c43131d91757dbe1c66"},{"sha":"05893712cc9950b7c4c312aa9d3d444375bf15a2","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Fix build under OPTIMIZER_DEBUG.\n\nIn commit 19a541143a09c067 I replaced RelOptInfo.width with\nRelOptInfo.reltarget.width, but I missed updating debug_print_rel()\nfor that because it's not compiled by default.\nReported by Salvador Fandino, patch by Michael Paquier.","distinct":false,"url":"https://api.github.com/repos/2ndQuadrant/postgres/commits/05893712cc9950b7c4c312aa9d3d444375bf15a2"},{"sha":"c110678a47aac87c661785a70061e160cd17713d","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Remove useless unary plus.\n\nIt's harmless, but might confuse readers.  Seems to have been introduced\nin 6bc8ef0b7f1f1df3.  Back-patch, just to avoid cosmetic cross-branch\ndifferences.\n\nAmit Langote","distinct":false,"url":"https://api.github.com/repos/2ndQuadrant/postgres/commits/c110678a47aac87c661785a70061e160cd17713d"},{"sha":"54638f5708e59e5fd7c79b8315d8c6e810d7bc13","author":{"email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org","name":"Alvaro Herrera"},"message":"Make new isolationtester test more stable\n\nThe original coding of the test was relying too much on the ordering in\nwhich backends are awakened once an advisory lock which they wait for is\nreleased.  Change the code so that each backend uses its own advisory\nlock instead, so that the output becomes stable.  Also add a few seconds\nof sleep between lock releases, so that the test isn't broken in\noverloaded buildfarm animals, as suggested by Tom Lane.\n\nPer buildfarm members spoonbill and guaibasaurus.\n\nDiscussion: https://www.postgresql.org/message-id/19294.1456551587%40sss.pgh.pa.us","distinct":false,"url":"https://api.github.com/repos/2ndQuadrant/postgres/commits/54638f5708e59e5fd7c79b8315d8c6e810d7bc13"},{"sha":"1c7c189fc1961f890bc06d6adb6bdfc739f5f927","author":{"email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org","name":"Alvaro Herrera"},"message":"doc: document MANPATH as /usr/local/pgsql/share/man\n\nThe docs were advising to use /usr/local/pgsql/man instead, but that's\nwrong.\n\nReported-By: Slawomir Sudnik\nBackpatch-To: 9.1\nBug: #13894","distinct":false,"url":"https://api.github.com/repos/2ndQuadrant/postgres/commits/1c7c189fc1961f890bc06d6adb6bdfc739f5f927"},{"sha":"10b4852215a37915e55f034f919a6dc8bc72e988","author":{"email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org","name":"Alvaro Herrera"},"message":"Fix typos\n\nAuthor: Amit Langote","distinct":false,"url":"https://api.github.com/repos/2ndQuadrant/postgres/commits/10b4852215a37915e55f034f919a6dc8bc72e988"},{"sha":"5847397deca66fb4a4b3d2e0dcb3414dd5c4e180","author":{"email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org","name":"Alvaro Herrera"},"message":"Minor tweaks for new src/test/recovery\n\nAuthor: Michael Paquier","distinct":false,"url":"https://api.github.com/repos/2ndQuadrant/postgres/commits/5847397deca66fb4a4b3d2e0dcb3414dd5c4e180"},{"sha":"8d8ff5f7db7d58240fac7d5f620308c91485b253","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Improve error message for rejecting RETURNING clauses with dropped columns.\n\nThis error message was written with only ON SELECT rules in mind, but since\nthen we also made RETURNING-clause targetlists go through the same logic.\nThis means that you got a rather off-topic error message if you tried to\nadd a rule with RETURNING to a table having dropped columns.  Ideally we'd\njust support that, but some preliminary investigation says that it might be\na significant amount of work.  Seeing that Nicklas Avén's complaint is the\nfirst one we've gotten about this in the ten years or so that the code's\nbeen like that, I'm unwilling to put much time into it.  Instead, improve\nthe error report by issuing a different message for RETURNING cases, and\nrevise the associated comment based on this investigation.\n\nDiscussion: 1456176604.17219.9.camel@jordogskog.no","distinct":false,"url":"https://api.github.com/repos/2ndQuadrant/postgres/commits/8d8ff5f7db7d58240fac7d5f620308c91485b253"},{"sha":"3d523564c53ab8f35edf4d20627f0a375a17624d","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Suppress scary-looking log messages from async-notify isolation test.\n\nI noticed that the async-notify test results in log messages like these:\n\nLOG:  could not send data to client: Broken pipe\nFATAL:  connection to client lost\n\nThis is because it unceremoniously disconnects a client session that is\nabout to have some NOTIFY messages delivered to it.  Such log messages\nduring a regression test might well cause people to go looking for a\nproblem that doesn't really exist (it did cause me to waste some time that\nway).  We can shut it up by adding an UNLISTEN command to session teardown.\n\nPatch HEAD only; this doesn't seem significant enough to back-patch.","distinct":false,"url":"https://api.github.com/repos/2ndQuadrant/postgres/commits/3d523564c53ab8f35edf4d20627f0a375a17624d"},{"sha":"9a3e06baa2e42a5018dcd6afda31255b4e772518","author":{"email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net","name":"Peter Eisentraut"},"message":"UCS_to_most.pl: Make executable, for consistency with other scripts","distinct":false,"url":"https://api.github.com/repos/2ndQuadrant/postgres/commits/9a3e06baa2e42a5018dcd6afda31255b4e772518"},{"sha":"cc074bf6c1a5305a5e23067c6d9a377840add303","author":{"email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net","name":"Peter Eisentraut"},"message":"Fix comments\n\nSome of these comments were copied and pasted without updating them,\nsome of them were duplicates.","distinct":false,"url":"https://api.github.com/repos/2ndQuadrant/postgres/commits/cc074bf6c1a5305a5e23067c6d9a377840add303"},{"sha":"bd6cf3f237c9aeb4dad1ac3ec2008c5768fe4c1b","author":{"email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net","name":"Peter Eisentraut"},"message":"Add Unicode map generation scripts as rule prerequisites\n\nThat way, the rules will trigger when the scripts change.","distinct":false,"url":"https://api.github.com/repos/2ndQuadrant/postgres/commits/bd6cf3f237c9aeb4dad1ac3ec2008c5768fe4c1b"},{"sha":"7e137f846df2431ce9c61202dcea21ee4a6d7822","author":{"email":"cc4ab156f0be9feefe10b35a552fd319cd7679ae@postgresql.org","name":"Robert Haas"},"message":"Extend pgbench's expression syntax to support a few built-in functions.\n\nFabien Coelho, reviewed mostly by Michael Paquier and me, but also by\nHeikki Linnakangas, BeomYong Lee, Kyotaro Horiguchi, Oleksander\nShulgin, and Álvaro Herrera.","distinct":false,"url":"https://api.github.com/repos/2ndQuadrant/postgres/commits/7e137f846df2431ce9c61202dcea21ee4a6d7822"},{"sha":"aec64e8f45209b084fa33482de3831bc68b18913","author":{"email":"cc4ab156f0be9feefe10b35a552fd319cd7679ae@postgresql.org","name":"Robert Haas"},"message":"Fix mistake in extensible node code.\n\nI believe that I (rhaas) introduced this bug while editing the patch\nthat became bcac23de73b89b001fbc628d84471a392e928d1c.\n\nReport and patch from KaiGai Kohei.","distinct":false,"url":"https://api.github.com/repos/2ndQuadrant/postgres/commits/aec64e8f45209b084fa33482de3831bc68b18913"},{"sha":"212bba93ce52e5605f8b7fc1ede2e7aef797c372","author":{"email":"cc4ab156f0be9feefe10b35a552fd319cd7679ae@postgresql.org","name":"Robert Haas"},"message":"Fix incorrect comment.\n\nPQmblen and PQdsplen return information about characters, not words.\n\nKyotaro Horiguchi","distinct":false,"url":"https://api.github.com/repos/2ndQuadrant/postgres/commits/212bba93ce52e5605f8b7fc1ede2e7aef797c372"},{"sha":"88802e068017bee8cea7a5502a712794e761c7b5","author":{"email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org","name":"Alvaro Herrera"},"message":"TAP tests: retain temp dirs on test failure\n\nThis makes it easier to study the reason for the failure.\n\nAuthor: Kyotaro Horiguchi\nReviewed-By: Craig Ringer","distinct":false,"url":"https://api.github.com/repos/2ndQuadrant/postgres/commits/88802e068017bee8cea7a5502a712794e761c7b5"},{"sha":"9def031bd2821f35b5f506260d922482648a8bb0","author":{"email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org","name":"Alvaro Herrera"},"message":"Add more tests for commit_timestamp feature\n\nThese tests verify that 1) WAL replay preserves the stored value,\n2) a streaming standby server replays the value obtained from the\nmaster, and 3) the behavior is sensible in the face of repeated\nconfiguration changes.\n\nOne annoyance is that tmp_check/ subdir from the TAP tests is clobbered\nwhen the pg_regress test runs in the same subdirectory.  This is\nbothersome but not too terrible a problem, since the pg_regress test is\nnot run anyway if the TAP tests fail (unless \"make -k\" is used).\n\nI had these tests around since commit 69e7235c93e2; add them now that we\nhave the recovery test framework in place.","distinct":false,"url":"https://api.github.com/repos/2ndQuadrant/postgres/commits/9def031bd2821f35b5f506260d922482648a8bb0"},{"sha":"68c521eb92c3515e3306f51a7fd3f32d16c97524","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Improve coverage of pltcl regression tests.\n\nTest composite-type arguments and the argisnull and spi_lastoid Tcl\ncommmands.  This stuff was not covered before, but needs to be exercised\nsince the upcoming Tcl object-conversion patch changes these code paths\n(and broke at least one of them).","distinct":false,"url":"https://api.github.com/repos/2ndQuadrant/postgres/commits/68c521eb92c3515e3306f51a7fd3f32d16c97524"},{"sha":"a892234f830e832110f63fc0a2afce2fb21d1584","author":{"email":"cc4ab156f0be9feefe10b35a552fd319cd7679ae@postgresql.org","name":"Robert Haas"},"message":"Change the format of the VM fork to add a second bit per page.\n\nThe new bit indicates whether every tuple on the page is already frozen.\nIt is cleared only when the all-visible bit is cleared, and it can be\nset only when we vacuum a page and find that every tuple on that page is\nboth visible to every transaction and in no need of any future\nvacuuming.\n\nA future commit will use this new bit to optimize away full-table scans\nthat would otherwise be triggered by XID wraparound considerations.  A\npage which is merely all-visible must still be scanned in that case, but\na page which is all-frozen need not be.  This commit does not attempt\nthat optimization, although that optimization is the goal here.  It\nseems better to get the basic infrastructure in place first.\n\nPer discussion, it's very desirable for pg_upgrade to automatically\nmigrate existing VM forks from the old format to the new format.  That,\ntoo, will be handled in a follow-on patch.\n\nMasahiko Sawada, reviewed by Kyotaro Horiguchi, Fujii Masao, Amit\nKapila, Simon Riggs, Andres Freund, and others, and substantially\nrevised by me.","distinct":false,"url":"https://api.github.com/repos/2ndQuadrant/postgres/commits/a892234f830e832110f63fc0a2afce2fb21d1584"}]}