{"push_id":1478492738,"size":12,"distinct_size":12,"ref":"refs/heads/logical_twophase","head":"df2d6f8d21a3f994721677fe613c6e1f80a14465","before":"de9cbb36272d56366978713f0e90115f92f3722f","commits":[{"sha":"86d216c77549e200b95bed487b6fb87d99a1e789","author":{"name":"Stephen Frost","email":"2063edcf0aa2fa8dfb7bba729d6cffa6fed14981@snowman.net"},"message":"pg_dumpall: Include --verbose option in --help output\n\nThe -v/--verbose option was not included in the output from --help for\npg_dumpall even though it's in the pg_dumpall documentation and has\napparently been around since pg_dumpall was reimplemented in C in 2002.\n\nFix that by adding it.\n\nPointed out by Daniel Westermann.\n\nBack-patch to all supported branches.\n\nDiscussion: https://www.postgresql.org/message-id/2020970042.4589542.1482482101585.JavaMail.zimbra%40dbi-services.com","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgres_cluster/commits/86d216c77549e200b95bed487b6fb87d99a1e789"},{"sha":"a3aef88e6a9c5822eb4a5ad0744b15dc6e8a5d86","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Fix incorrect error reporting for duplicate data in \\crosstabview.\n\n\\crosstabview's complaint about multiple entries for the same crosstab\ncell quoted the wrong row and/or column values.  It would accidentally\nappear to work if the data had been in strcmp() order to start with,\nwhich probably explains how we missed noticing this during development.\n\nThis could be fixed in more than one way, but the way I chose was to\nhang onto both result pointers from bsearch() and use those to get at\nthe value names.\n\nIn passing, avoid casting away const in the bsearch comparison functions.\nNo bug there, just poor style.\n\nPer bug #14476 from Tomonari Katsumata.  Back-patch to 9.6 where\n\\crosstabview was introduced.\n\nReport: https://postgr.es/m/20161225021519.10139.45460@wrigleys.postgresql.org","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgres_cluster/commits/a3aef88e6a9c5822eb4a5ad0744b15dc6e8a5d86"},{"sha":"54386f3578258caa5a1de97c434eee2c9ee2ab06","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Remove triggerable Assert in hashname().\n\nhashname() asserted that the key string it is given is shorter than\nNAMEDATALEN.  That should surely always be true if the input is in fact a\nregular value of type \"name\".  However, for reasons of coding convenience,\nwe allow plain old C strings to be treated as \"name\" values in many places.\nSome SQL functions accept arbitrary \"text\" inputs, convert them to C\nstrings, and pass them otherwise-untransformed to syscache lookups for name\ncolumns, allowing an overlength input value to trigger hashname's Assert.\n\nThis would be a DOS problem, except that it only happens in assert-enabled\nbuilds which aren't recommended for production.  In a production build,\nyou'll just get a name lookup error, since regardless of the hash value\ncomputed by hashname, the later equality comparison checks can't match.\nLikewise, if the catalog lookup is done by seqscan or indexscan searches,\nthere will just be a lookup error, since the name comparison functions\ndon't contain any similar length checks, and will see an overlength input\nas unequal to any stored entry.\n\nAfter discussion we concluded that we should simply remove this Assert.\nIt's inessential to hashname's own functionality, and having such an\nassertion in only some paths for name lookup is more of a foot-gun than\na useful check.  There may or may not be a case for the affected callers\nto do something other than let the name lookup fail, but we'll consider\nthat separately; in any case we probably don't want to change such\nbehavior in the back branches.\n\nPer report from Tushar Ahuja.  Back-patch to all supported branches.\n\nReport: https://postgr.es/m/7d0809ee-6f25-c9d6-8e74-5b2967830d49@enterprisedb.com\nDiscussion: https://postgr.es/m/17691.1482523168@sss.pgh.pa.us","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgres_cluster/commits/54386f3578258caa5a1de97c434eee2c9ee2ab06"},{"sha":"6cfa54e384700d4a2124e5c4d7a1eb91e8e0eeb7","author":{"name":"Magnus Hagander","email":"96ad6b06de7111eee5a9c968ba6978bf7a7a179d@hagander.net"},"message":"Fix typo comments\n\nErik Rijkers","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgres_cluster/commits/6cfa54e384700d4a2124e5c4d7a1eb91e8e0eeb7"},{"sha":"3ea56fffd66fe2c5857f36359ae16d4cabcdeef6","author":{"name":"Magnus Hagander","email":"96ad6b06de7111eee5a9c968ba6978bf7a7a179d@hagander.net"},"message":"Don't rename .partial files in pg_receivexlog if an error occured\n\nIn 56c7d8d the behavior to keep .partial segments around\n(considered corrupt) in case an connection failure occurs was\naccidentally removed. This would lead to an incomplete segment\nbeing considered complete.\n\nAuthor: Michael Paquier","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgres_cluster/commits/3ea56fffd66fe2c5857f36359ae16d4cabcdeef6"},{"sha":"71f996d22125eb6cfdbee6094f44370aa8dec610","author":{"name":"Andrew Dunstan","email":"6b7c097d961f68685fc978cf91eeae17be6cbb45@dunslane.net"},"message":"Explain unaccounted for space in pgstattuple.\n\nIn addition to space accounted for by tuple_len, dead_tuple_len and\nfree_space, the table_len includes page overhead, the item pointers\ntable and padding bytes.\n\nBackpatch to live branches.","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgres_cluster/commits/71f996d22125eb6cfdbee6094f44370aa8dec610"},{"sha":"f0774abde868e0b5a2acbe75b5028884752f739d","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Fix interval_transform so it doesn't throw away non-no-op casts.\n\ninterval_transform() contained two separate bugs that caused it to\nsometimes mistakenly decide that a cast from interval to restricted\ninterval is a no-op and throw it away.\n\nFirst, it was wrong to rely on dt.h's field type macros to have an\nordering consistent with the field's significance; in one case they do\nnot.  This led to mistakenly treating YEAR as less significant than MONTH,\nso that a cast from INTERVAL MONTH to INTERVAL YEAR was incorrectly\ndiscarded.\n\nSecond, fls(1<<k) produces k+1 not k, so comparing its output directly\nto SECOND was wrong.  This led to supposing that a cast to INTERVAL\nMINUTE was really a cast to INTERVAL SECOND and so could be discarded.\n\nTo fix, get rid of the use of fls(), and make a function based on\nintervaltypmodout to produce a field ID code adapted to the need here.\n\nPer bug #14479 from Piotr Stefaniak.  Back-patch to 9.2 where transform\nfunctions were introduced, because this code was born broken.\n\nDiscussion: https://postgr.es/m/20161227172307.10135.7747@wrigleys.postgresql.org","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgres_cluster/commits/f0774abde868e0b5a2acbe75b5028884752f739d"},{"sha":"1ec39c71a185890b4979b05ccebb44f27ed7d542","author":{"name":"Stas Kelvich","email":"0561c2c5a3d5ff702bda372a0a13fe9520f10363@gmail.com"},"message":"applied old patch","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgres_cluster/commits/1ec39c71a185890b4979b05ccebb44f27ed7d542"},{"sha":"85a83ef767a4f9aa4873a49b030e835057cfee0d","author":{"name":"Stas Kelvich","email":"0561c2c5a3d5ff702bda372a0a13fe9520f10363@gmail.com"},"message":"use brand new verlen gid","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgres_cluster/commits/85a83ef767a4f9aa4873a49b030e835057cfee0d"},{"sha":"270eee5a201d2c081add72a65cc5d8b89825430f","author":{"name":"Stas Kelvich","email":"0561c2c5a3d5ff702bda372a0a13fe9520f10363@gmail.com"},"message":"add 2pc to test_decoding","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgres_cluster/commits/270eee5a201d2c081add72a65cc5d8b89825430f"},{"sha":"1a23a459d4c7d01015bf069231d12b2885574319","author":{"name":"Stas Kelvich","email":"0561c2c5a3d5ff702bda372a0a13fe9520f10363@gmail.com"},"message":"some fixes","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgres_cluster/commits/1a23a459d4c7d01015bf069231d12b2885574319"},{"sha":"df2d6f8d21a3f994721677fe613c6e1f80a14465","author":{"name":"Stas Kelvich","email":"0561c2c5a3d5ff702bda372a0a13fe9520f10363@gmail.com"},"message":"merge","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgres_cluster/commits/df2d6f8d21a3f994721677fe613c6e1f80a14465"}]}
{"actor":{"display_login":"kelvich"}}