{"push_id":1282380418,"size":8,"distinct_size":8,"ref":"refs/heads/master","head":"5a072244919a92b2c757b2e3985191f02d674627","before":"39b691f251167bbb3d49203abfb39d430f68f411","commits":[{"sha":"0c40ab3a88edf654165e562deee0c303a6ebef5e","author":{"name":"Simon Riggs","email":"3a69a7dd305e9c7705028afae27095688d25197a@2ndQuadrant.com"},"message":"Fix wording of logical decoding concepts\n\nBe specific about conditions under which we emit >1 copy of message\n\nCraig Ringer","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/0c40ab3a88edf654165e562deee0c303a6ebef5e"},{"sha":"35250b6ad7a8ece5cfe54c0316c180df19f36c13","author":{"name":"Simon Riggs","email":"3a69a7dd305e9c7705028afae27095688d25197a@2ndQuadrant.com"},"message":"New recovery target recovery_target_lsn\n\nMichael Paquier","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/35250b6ad7a8ece5cfe54c0316c180df19f36c13"},{"sha":"60893786d5180f5dd5aefd44d9cb6955d77b0473","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Fix corrupt GIN_SEGMENT_ADDITEMS WAL records on big-endian hardware.\n\ncomputeLeafRecompressWALData() tried to produce a uint16 WAL log field by\nmemcpy'ing the first two bytes of an int-sized variable.  That accidentally\nworks on little-endian hardware, but not at all on big-endian.  Replay then\nthinks it's looking at an ADDITEMS action with zero entries, and reads the\nfirst two bytes of the first TID therein as the next segno/action,\ntypically leading to \"unexpected GIN leaf action\" errors during replay.\nEven if replay failed to crash, the resulting GIN index page would surely\nbe incorrect.  To fix, just declare the variable as uint16 instead.\n\nPer bug #14295 from Spencer Thomason (much thanks to Spencer for turning\nhis problem into a self-contained test case).  This likely also explains\na previous report of the same symptom from Bernd Helmle.\n\nBack-patch to 9.4 where the problem was introduced (by commit 14d02f0bb).\n\nDiscussion: <20160826072658.15676.7628@wrigleys.postgresql.org>\nPossible-Report: <2DA7350F7296B2A142272901@eje.land.credativ.lan>","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/60893786d5180f5dd5aefd44d9cb6955d77b0473"},{"sha":"600dc4c0da3b8c094ccc1ae75b47c8320898c714","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Fix multiple bugs in numeric_poly_deserialize().\n\nThese were evidently introduced by yesterday's commit 9cca11c91,\nwhich perhaps needs more review than it got.\n\nPer report from Andreas Seltenreich and additional examination\nof nearby code.\n\nReport: <87oa45qfwq.fsf@credativ.de>","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/600dc4c0da3b8c094ccc1ae75b47c8320898c714"},{"sha":"6591f4226c81104f7746da6a5c00519919c560ae","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Improve readability of the output of psql's \\timing command.\n\nIn addition to the existing decimal-milliseconds output value,\ndisplay the same value in mm:ss.fff format if it exceeds one second.\nTack on hours and even days fields if the interval is large enough.\nThis avoids needing mental arithmetic to convert the values into\ncustomary time units.\n\nCorey Huinker, reviewed by Gerdan Santos; bikeshedding by many\n\nDiscussion: <CADkLM=dbC4R8sbbuFXQVBFWoJGQkTEW8RWnC0PbW9nZsovZpJQ@mail.gmail.com>","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/6591f4226c81104f7746da6a5c00519919c560ae"},{"sha":"e21db14b8a6696a2b704b89df9c4be9cd0ea8a33","author":{"name":"Heikki Linnakangas","email":"f503d7d54583b01050f859fedbc50f86f41cf34b@iki.fi"},"message":"Clarify the new Red-Black post-order traversal code a bit.\n\nCoverity complained about the for(;;) loop, because it never actually\niterated. It was used just to be able to use \"break\" to exit it early. I\nagree with Coverity, that's a bit confusing, so refactor the code to\nuse if-else instead.\n\nWhile we're at it, use a local variable to hold the \"current\" node. That's\nshorter and clearer than referring to \"iter->last_visited\" all the time.","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/e21db14b8a6696a2b704b89df9c4be9cd0ea8a33"},{"sha":"a2d75b67bccd24d17e328360080e4877d23bc369","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Remove useless pg_strdup() operations.\n\nsplit_to_stringlist() doesn't modify its first argument nor expect it\nto remain valid after exit, so there's no need to duplicate the optarg\nstring at the call sites.  Per Coverity.  (This has been wrong all along,\nbut commit 052cc223d changed the useless calls from \"strdup\" to\n\"pg_strdup\", which apparently made Coverity think it's a new bug.\nIt's not, but it's also not worth back-patching.)","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/a2d75b67bccd24d17e328360080e4877d23bc369"},{"sha":"5a072244919a92b2c757b2e3985191f02d674627","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Update release notes to mention need for ALTER EXTENSION UPDATE.\n\nMaybe we ought to make pg_upgrade do this for you, but it won't happen\nin 9.6, so call out the need for it as a migration consideration.","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/5a072244919a92b2c757b2e3985191f02d674627"}]}
{"actor":{"display_login":"tvondra"}}