{"push_id":892290807,"size":30,"distinct_size":30,"ref":"refs/heads/master","head":"0e0776bc99553ff229e0d536ed8c78ab9db62464","before":"d3c8ac114f1183e54315e64ef697c6588823c4dd","commits":[{"sha":"7907a949abf100b5a1e1def1184ba1e6fc8b9fd7","author":{"email":"cc4ab156f0be9feefe10b35a552fd319cd7679ae@postgresql.org","name":"Robert Haas"},"message":"Fix incomplete set_foreignscan_references handling for fdw_recheck_quals\n\nKaiGai Kohei","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/7907a949abf100b5a1e1def1184ba1e6fc8b9fd7"},{"sha":"d835dd6685246f0737ca42ab68242210681bb220","author":{"email":"02e0a999c50b1f88df7a8f5a04e1b76b35ea6a88@dunslane.net","name":"Andrew Dunstan"},"message":"Improve vcregress.pl's handling of tap tests for client programs\n\nThe target is now named 'bincheck' rather than 'tapcheck' so that it\nreflects what is checked instead of the test mechanism. Some of the\nlogic is improved, making it easier to add further sets of TAP based\ntests in future. Also, the environment setting logic is imrpoved.\n\nAs discussed on -hackers a couple of months ago.","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/d835dd6685246f0737ca42ab68242210681bb220"},{"sha":"c2d5657c0f6f8ae9894205551354eca796f8b11c","author":{"email":"02e0a999c50b1f88df7a8f5a04e1b76b35ea6a88@dunslane.net","name":"Andrew Dunstan"},"message":"Update docs for vcregress.pl bincheck changes","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/c2d5657c0f6f8ae9894205551354eca796f8b11c"},{"sha":"f11c557e92c50d3d613d1173c15feb5310ba4744","author":{"email":"02e0a999c50b1f88df7a8f5a04e1b76b35ea6a88@dunslane.net","name":"Andrew Dunstan"},"message":"fix a perl typo","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/f11c557e92c50d3d613d1173c15feb5310ba4744"},{"sha":"bc4996e61b98d41eacf991c18508b7a2305a68c6","author":{"email":"cc4ab156f0be9feefe10b35a552fd319cd7679ae@postgresql.org","name":"Robert Haas"},"message":"Make ALTER .. SET SCHEMA do nothing, instead of throwing an ERROR.\n\nThis was already true for CREATE EXTENSION, but historically has not\nbeen true for other object types.  Therefore, this is a backward\nincompatibility.  Per discussion on pgsql-hackers, everyone seems to\nagree that the new behavior is better.\n\nMarti Raudsepp, reviewed by Haribabu Kommi and myself","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/bc4996e61b98d41eacf991c18508b7a2305a68c6"},{"sha":"9be3a4e24dc777e31f6358907ebefac841ea2632","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Fix thinko: errmsg -> ereport.\n\nSilly mistake in my commit 09cecdf285ea9f51, reported by Erik Rijkers.\n\nThe fact that the buildfarm didn't find this implies that we are not\ntesting Perl builds that lack MULTIPLICITY, which is a bit disturbing\nfrom a coverage standpoint.  Until today I'd have said nobody cared\nabout such configurations anymore; but maybe not.","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/9be3a4e24dc777e31f6358907ebefac841ea2632"},{"sha":"db135e834a28180e9151f12c694b07d8fc3c41a8","author":{"email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net","name":"Peter Eisentraut"},"message":"doc: Clarify some things on pg_receivexlog reference page","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/db135e834a28180e9151f12c694b07d8fc3c41a8"},{"sha":"68c1d7d42e553682f1d2723e623b6a3a4b02c75f","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Dodge a macro-name conflict with Perl.\n\nSome versions of Perl export a macro named HS_KEY.  This creates a\nconflict in contrib/hstore_plperl against hstore's macro of the same\nname.  The most future-proof solution seems to be to rename our macro;\nI chose HSTORE_KEY.  For consistency, rename HS_VAL and related macros\nsimilarly.\n\nBack-patch to 9.5.  contrib/hstore_plperl doesn't exist before that\nso there is no need to worry about the conflict in older releases.\n\nPer reports from Marco Atzeri and Mike Blackwell.","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/68c1d7d42e553682f1d2723e623b6a3a4b02c75f"},{"sha":"fea2b642fdb1bbe0f4b1bd0a763c370dfc6fb97c","author":{"email":"cc4ab156f0be9feefe10b35a552fd319cd7679ae@postgresql.org","name":"Robert Haas"},"message":"Remove numbers from incorrectly-numbered list.\n\nReported by Andres Freund.","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/fea2b642fdb1bbe0f4b1bd0a763c370dfc6fb97c"},{"sha":"74d0d5f3ebed9d817ec353fb17eedb343a0ab5b4","author":{"email":"cc4ab156f0be9feefe10b35a552fd319cd7679ae@postgresql.org","name":"Robert Haas"},"message":"Fix typo in comment.\n\nAmit Langote","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/74d0d5f3ebed9d817ec353fb17eedb343a0ab5b4"},{"sha":"6c878a7553680579f287e4659592c0b874fb2377","author":{"email":"cc4ab156f0be9feefe10b35a552fd319cd7679ae@postgresql.org","name":"Robert Haas"},"message":"Avoid server crash when worker registration fails at execution time.\n\nThe previous coding attempts to destroy the DSM in this case, but\nchild nodes might have stored data there and still be holding onto\npointers in this case.  So don't do that.\n\nAlso, free the reader array instead of leaking it.\n\nExtracted from two different patch versions both by Amit Kapila.","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/6c878a7553680579f287e4659592c0b874fb2377"},{"sha":"074c5cfbfb4923158be9ccdb77420d6522d77538","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Fix handling of inherited check constraints in ALTER COLUMN TYPE (again).\n\nThe previous way of reconstructing check constraints was to do a separate\n\"ALTER TABLE ONLY tab ADD CONSTRAINT\" for each table in an inheritance\nhierarchy.  However, that way has no hope of reconstructing the check\nconstraints' own inheritance properties correctly, as pointed out in\nbug #13779 from Jan Dirk Zijlstra.  What we should do instead is to do\na regular \"ALTER TABLE\", allowing recursion, at the topmost table that\nhas a particular constraint, and then suppress the work queue entries\nfor inherited instances of the constraint.\n\nAnnoyingly, we'd tried to fix this behavior before, in commit 5ed6546cf,\nbut we failed to notice that it wasn't reconstructing the pg_constraint\nfield values correctly.\n\nAs long as I'm touching pg_get_constraintdef_worker anyway, tweak it to\nalways schema-qualify the target table name; this seems like useful backup\nto the protections installed by commit 5f173040.\n\nIn HEAD/9.5, get rid of get_constraint_relation_oids, which is now unused.\n(I could alternatively have modified it to also return conislocal, but that\nseemed like a pretty single-purpose API, so let's not pretend it has some\nother use.)  It's unused in the back branches as well, but I left it in\nplace just in case some third-party code has decided to use it.\n\nIn HEAD/9.5, also rename pg_get_constraintdef_string to\npg_get_constraintdef_command, as the previous name did nothing to explain\nwhat that entry point did differently from others (and its comment was\nequally useless).  Again, that change doesn't seem like material for\nback-patching.\n\nI did a bit of re-pgindenting in tablecmds.c in HEAD/9.5, as well.\n\nOtherwise, back-patch to all supported branches.","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/074c5cfbfb4923158be9ccdb77420d6522d77538"},{"sha":"00cdd83521cfdaaff0f566ebeadecc2cad4d51cf","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Adopt the GNU convention for handling tar-archive members exceeding 8GB.\n\nThe POSIX standard for tar headers requires archive member sizes to be\nprinted in octal with at most 11 digits, limiting the representable file\nsize to 8GB.  However, GNU tar and apparently most other modern tars\nsupport a convention in which oversized values can be stored in base-256,\nallowing any practical file to be a tar member.  Adopt this convention\nto remove two limitations:\n* pg_dump with -Ft output format failed if the contents of any one table\nexceeded 8GB.\n* pg_basebackup failed if the data directory contained any file exceeding\n8GB.  (This would be a fatal problem for installations configured with a\ntable segment size of 8GB or more, and it has also been seen to fail when\nlarge core dump files exist in the data directory.)\n\nFile sizes under 8GB are still printed in octal, so that no compatibility\nissues are created except in cases that would have failed entirely before.\n\nIn addition, this patch fixes several bugs in the same area:\n\n* In 9.3 and later, we'd defined tarCreateHeader's file-size argument as\nsize_t, which meant that on 32-bit machines it would write a corrupt tar\nheader for file sizes between 4GB and 8GB, even though no error was raised.\nThis broke both \"pg_dump -Ft\" and pg_basebackup for such cases.\n\n* pg_restore from a tar archive would fail on tables of size between 4GB\nand 8GB, on machines where either \"size_t\" or \"unsigned long\" is 32 bits.\nThis happened even with an archive file not affected by the previous bug.\n\n* pg_basebackup would fail if there were files of size between 4GB and 8GB,\neven on 64-bit machines.\n\n* In 9.3 and later, \"pg_basebackup -Ft\" failed entirely, for any file size,\non 64-bit big-endian machines.\n\nIn view of these potential data-loss bugs, back-patch to all supported\nbranches, even though removal of the documented 8GB limit might otherwise\nbe considered a new feature rather than a bug fix.","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/00cdd83521cfdaaff0f566ebeadecc2cad4d51cf"},{"sha":"2ef7a985fb9077aabeb480a23732c4d6ddb89ce5","author":{"email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net","name":"Peter Eisentraut"},"message":"doc: Add more documentation about wal_retrieve_retry_interval\n\nfrom Michael Paquier","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/2ef7a985fb9077aabeb480a23732c4d6ddb89ce5"},{"sha":"d00352573a1d5cf685397d5776c36b625c3f0c79","author":{"email":"231337598724646720571a00c656f975fff6a8f2@sigaev.ru","name":"Teodor Sigaev"},"message":"Clarify pg_rewind connection requirements.\n\nPer http://www.postgresql.org/message-id/flat/564C4CE6.9000509@postgrespro.ru\nPavel Luzanov <p.luzanov@postgrespro.ru>","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/d00352573a1d5cf685397d5776c36b625c3f0c79"},{"sha":"cbd96eff251bf92e88a13ef00df07c6caae0d411","author":{"email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net","name":"Peter Eisentraut"},"message":"doc: Some improvements on CREATE POLICY and ALTER POLICY documentation","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/cbd96eff251bf92e88a13ef00df07c6caae0d411"},{"sha":"13b30c16f3164ee70599adee251256bd069fa0e4","author":{"email":"9ae9c44b775ee9b29f4f502415e02e61a9b1a6a0@momjian.us","name":"Bruce Momjian"},"message":"pg_upgrade:  fix CopyFile() on Windows to fail on file existence\n\nAlso fix getErrorText() to return the right error string on failure.\nThis behavior now matches that of other operating systems.\n\nReport by Noah Misch\n\nBackpatch through 9.1","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/13b30c16f3164ee70599adee251256bd069fa0e4"},{"sha":"d6061f83a166b015657fda8623c704fcb86930e9","author":{"email":"231337598724646720571a00c656f975fff6a8f2@sigaev.ru","name":"Teodor Sigaev"},"message":"Improve pageinspect module\n\nNow pageinspect can show data stored in the heap tuple.\n\nNikolay Shaplov","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/d6061f83a166b015657fda8623c704fcb86930e9"},{"sha":"0271e27c1089f104236a7fe3b3fca52e5359ae56","author":{"email":"231337598724646720571a00c656f975fff6a8f2@sigaev.ru","name":"Teodor Sigaev"},"message":"Add forgotten file in commit d6061f83a166b015657fda8623c704fcb86930e9","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/0271e27c1089f104236a7fe3b3fca52e5359ae56"},{"sha":"46166197c3b3748c3266c694d7c2f5a312ea928e","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Improve div_var_fast(), mostly by making comments better.\n\nThe integer overflow situation in div_var_fast() is a great deal more\ncomplicated than the pre-existing comments would suggest.  Moreover, the\ncomments were also flat out incorrect as to the precise statement of the\nmaxdiv loop invariant.  Upon clarifying that, it becomes apparent that the\nway in which we updated maxdiv after a carry propagation pass was overly\nslow, complex, and conservative: we can just reset it to one, which is much\neasier and also reduces the number of times carry propagation occurs.\nFix that and improve the relevant comments.\n\nSince this is mostly a comment fix, with only a rather marginal performance\nboost, no need for back-patch.\n\nTom Lane and Dean Rasheed","distinct":true,"url":"https://api.github.com/repos/tvondra/postgres/commits/46166197c3b3748c3266c694d7c2f5a312ea928e"}]}