{"push_id":1130640803,"size":43,"distinct_size":43,"ref":"refs/heads/PGPRO9_5_ptrack","head":"4ee2ad87d49a222f1781ecd66a231a7c930c3833","before":"3489eee634786d173b73e5da1e95e843f6dcf0e2","commits":[{"sha":"7516cdb76adb0710b0453d6b5252f14fc8ca49bc","author":{"email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org","name":"Alvaro Herrera"},"message":"Fix autovacuum for shared relations\n\nThe table-skipping logic in autovacuum would fail to consider that\nmultiple workers could be processing the same shared catalog in\ndifferent databases.  This normally wouldn't be a problem: firstly\nbecause autovacuum workers not for wraparound would simply ignore tables\nin which they cannot acquire lock, and secondly because most of the time\nthese tables are small enough that even if multiple for-wraparound\nworkers are stuck in the same catalog, they would be over pretty\nquickly.  But in cases where the catalogs are severely bloated it could\nbecome a problem.\n\nBackpatch all the way back, because the problem has been there since the\nbeginning.\n\nReported by Ondřej Světlík\n\nDiscussion: https://www.postgresql.org/message-id/572B63B1.3030603%40flexibee.eu\n\thttps://www.postgresql.org/message-id/572A1072.5080308%40flexibee.eu","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgrespro/commits/7516cdb76adb0710b0453d6b5252f14fc8ca49bc"},{"sha":"52a262b5f131a1a8c4fab85b2c737749d2cd6b29","author":{"email":"a2a7edff87562dbd669279774e32ef9f61cfc574@wagner.pp.ru","name":"Victor Wagner"},"message":"Merge branch 'REL9_5_STABLE' into PGPRO9_5","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgrespro/commits/52a262b5f131a1a8c4fab85b2c737749d2cd6b29"},{"sha":"612203db459e7f0aa118e79c05bfccf84faab0d8","author":{"email":"a2a7edff87562dbd669279774e32ef9f61cfc574@wagner.pp.ru","name":"Victor Wagner"},"message":"Release notes for Postgres Pro 9.5.3.1 (en)","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgrespro/commits/612203db459e7f0aa118e79c05bfccf84faab0d8"},{"sha":"58d802410ad85c44073d4ef494a9d5ac24ecba66","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Fix assorted missing infrastructure for ON CONFLICT.\n\nsubquery_planner() failed to apply expression preprocessing to the\narbiterElems and arbiterWhere fields of an OnConflictExpr.  No doubt the\ntheory was that this wasn't necessary because we don't actually try to\nexecute those expressions; but that's wrong, because it results in failure\nto match to index expressions or index predicates that are changed at all\nby preprocessing.  Per bug #14132 from Reynold Smith.\n\nAlso add pullup_replace_vars processing for onConflictWhere.  Perhaps\nit's impossible to have a subquery reference there, but I'm not exactly\nconvinced; and even if true today it's a failure waiting to happen.\n\nAlso add some comments to other places where one or another field of\nOnConflictExpr is intentionally ignored, with explanation as to why it's\nokay to do so.\n\nAlso, catalog/dependency.c failed to record any dependency on the named\nconstraint in ON CONFLICT ON CONSTRAINT, allowing such a constraint to\nbe dropped while rules exist that depend on it, and allowing pg_dump to\ndump such a rule before the constraint it refers to.  The normal execution\npath managed to error out reasonably for a dangling constraint reference,\nbut ruleutils.c dumped core; so in addition to fixing the omission, add\na protective check in ruleutils.c, since we can't retroactively add a\ndependency in existing databases.\n\nBack-patch to 9.5 where this code was introduced.\n\nReport: <20160510190350.2608.48667@wrigleys.postgresql.org>","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgrespro/commits/58d802410ad85c44073d4ef494a9d5ac24ecba66"},{"sha":"428484ce102b3d4e6308c8504744558c2e2d99af","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Fix infer_arbiter_indexes() to not barf on system columns.\n\nWhile it could be argued that rejecting system column mentions in the\nON CONFLICT list is an unsupported feature, falling over altogether\njust because the table has a unique index on OID is indubitably a bug.\n\nAs far as I can tell, fixing infer_arbiter_indexes() is sufficient to\nmake ON CONFLICT (oid) actually work, though making a regression test\nfor that case is problematic because of the impossibility of setting\nthe OID counter to a known value.\n\nMinor cosmetic cleanups along with the bug fix.","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgrespro/commits/428484ce102b3d4e6308c8504744558c2e2d99af"},{"sha":"ed34a976e2d1fa086f2d0a9cab9caaf36d378d81","author":{"email":"a2a7edff87562dbd669279774e32ef9f61cfc574@wagner.pp.ru","name":"Victor Wagner"},"message":"Described pgpro_upgrade in release notes","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgrespro/commits/ed34a976e2d1fa086f2d0a9cab9caaf36d378d81"},{"sha":"649fb87d4e0b6e41eafed50092024e8cb1ec0d2b","author":{"email":"a2a7edff87562dbd669279774e32ef9f61cfc574@wagner.pp.ru","name":"Victor Wagner"},"message":"Fixed some typos in the release notes","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgrespro/commits/649fb87d4e0b6e41eafed50092024e8cb1ec0d2b"},{"sha":"f00ab8d6008bb4b3f7e833bf90bf1ed9209b9df1","author":{"email":"a2a7edff87562dbd669279774e32ef9f61cfc574@wagner.pp.ru","name":"Victor Wagner"},"message":"Fixed cases where PostgresPro was written without space","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgrespro/commits/f00ab8d6008bb4b3f7e833bf90bf1ed9209b9df1"},{"sha":"ca7251bc2dccd3d2c6783b86dace7e7c31754dd6","author":{"email":"a2a7edff87562dbd669279774e32ef9f61cfc574@wagner.pp.ru","name":"Victor Wagner"},"message":"Typos in the release notes, found during translation","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgrespro/commits/ca7251bc2dccd3d2c6783b86dace7e7c31754dd6"},{"sha":"21ef195340bf37cb55383f6fdfe33609f5003a27","author":{"email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org","name":"Alvaro Herrera"},"message":"Fix obsolete comment","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgrespro/commits/21ef195340bf37cb55383f6fdfe33609f5003a27"},{"sha":"4140619df909ed90f485c0e96a5c4b901e544976","author":{"email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org","name":"Alvaro Herrera"},"message":"Fix bogus comments\n\nSome comments mentioned XLogReplayBuffer, but there's no such function:\nthat was an interim name for a function that got renamed to\nXLogReadBufferForRedo, before commit 2c03216d831160 was pushed.","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgrespro/commits/4140619df909ed90f485c0e96a5c4b901e544976"},{"sha":"ab5f73b3ea3180959bb265811c6ac1d535c6f01c","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Ensure plan stability in contrib/btree_gist regression test.\n\nBuildfarm member skink failed with symptoms suggesting that an\nauto-analyze had happened and changed the plan displayed for a\ntest query.  Although this is evidently of low probability,\nregression tests that sometimes fail are no fun, so add commands\nto force a bitmap scan to be chosen.","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgrespro/commits/ab5f73b3ea3180959bb265811c6ac1d535c6f01c"},{"sha":"779f39218429a26616ec410cbccbdcf95b2d37a6","author":{"email":"a2a7edff87562dbd669279774e32ef9f61cfc574@wagner.pp.ru","name":"Victor Wagner"},"message":"Added pathman docs","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgrespro/commits/779f39218429a26616ec410cbccbdcf95b2d37a6"},{"sha":"498b7bba0272268f5201b343e2f99eb06afec26c","author":{"email":"a2a7edff87562dbd669279774e32ef9f61cfc574@wagner.pp.ru","name":"Victor Wagner"},"message":"Fix some typos in pg_variables doc","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgrespro/commits/498b7bba0272268f5201b343e2f99eb06afec26c"},{"sha":"9312c04ac0162ce50a175bba8d1ab9ba023b5770","author":{"email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net","name":"Peter Eisentraut"},"message":"doc: Fix typo\n\nFrom: Alexander Law <exclusion@gmail.com>","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgrespro/commits/9312c04ac0162ce50a175bba8d1ab9ba023b5770"},{"sha":"d74c089193392de37c90b14d805b42ec46725be2","author":{"email":"a2a7edff87562dbd669279774e32ef9f61cfc574@wagner.pp.ru","name":"Victor Wagner"},"message":"Fixed bug reporting address. Use PGPRO_VERSION when generate version.sgml","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgrespro/commits/d74c089193392de37c90b14d805b42ec46725be2"},{"sha":"daebcbc896ec891cc60c3292de16ee95d666fc2e","author":{"email":"a2a7edff87562dbd669279774e32ef9f61cfc574@wagner.pp.ru","name":"Victor Wagner"},"message":"Use PGPRO_VERSION when generating windows help file","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgrespro/commits/daebcbc896ec891cc60c3292de16ee95d666fc2e"},{"sha":"e6ef391e26ae33a0732ee1c2fe688dbfa673fefc","author":{"email":"6cd23306da735b22de5e046cd21b442304186573@gmail.com","name":"Ivan Panchenko"},"message":"Added \"Postgres Pro vs PostgreSQL\" page.\nPlease provide the feature list with xrefs.","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgrespro/commits/e6ef391e26ae33a0732ee1c2fe688dbfa673fefc"},{"sha":"6221389eb64e7336b3110f0b5a87cc9d2493d16a","author":{"email":"a2a7edff87562dbd669279774e32ef9f61cfc574@wagner.pp.ru","name":"Victor Wagner"},"message":"Fix sgml errors","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgrespro/commits/6221389eb64e7336b3110f0b5a87cc9d2493d16a"},{"sha":"77b99228fe9c7e38dd65d2bef5a3bf5a2d558b69","author":{"email":"a2a7edff87562dbd669279774e32ef9f61cfc574@wagner.pp.ru","name":"Victor Wagner"},"message":"period after simpara","distinct":true,"url":"https://api.github.com/repos/postgrespro/postgrespro/commits/77b99228fe9c7e38dd65d2bef5a3bf5a2d558b69"}]}
{"actor":{"display_login":"stalkerg"}}