{"push_id":1202707236,"size":11,"distinct_size":11,"ref":"refs/heads/master","head":"56a997413391337f7fb9926144d6b6fa831b9d22","before":"ae7d78c3e24d7991a8f76f4676c015df3d143d63","commits":[{"sha":"740bf396a1d5cc41a8398076a9de1485c497c49c","author":{"name":"Peter Eisentraut","email":"2f47089682e4afbd5de3eea4edffc95dfc1eb9de@gmx.net"},"message":"doc: Update URL for PL/PHP","distinct":true,"url":"https://api.github.com/repos/glukhovn/postgres/commits/740bf396a1d5cc41a8398076a9de1485c497c49c"},{"sha":"a670c24c382693c4f75e99c9292b2ed0f0d40a72","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Improve output of psql's \\df+ command.\n\nAdd display of proparallel (parallel-safety) when the server is >= 9.6,\nand display of proacl (access privileges) for all server versions.\nMinor tweak of column ordering to keep related columns together.\n\nMichael Paquier\n\nDiscussion: <CAB7nPqTR3Vu3xKOZOYqSm-+bSZV0kqgeGAXD6w5GLbkbfd5Q6w@mail.gmail.com>","distinct":true,"url":"https://api.github.com/repos/glukhovn/postgres/commits/a670c24c382693c4f75e99c9292b2ed0f0d40a72"},{"sha":"4d042999f94a4bc41b86baca5920cd4829e16895","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Print a given subplan only once in EXPLAIN.\n\nWe have, for a very long time, allowed the same subplan (same member of the\nPlannedStmt.subplans list) to be referenced by more than one SubPlan node;\nthis avoids problems for cases such as subplans within an IndexScan's\nindxqual and indxqualorig fields.  However, EXPLAIN had not gotten the memo\nand would print each reference as though it were an independent identical\nsubplan.  To fix, track plan_ids of subplans we've printed and don't print\nthe same plan_id twice.  Per report from Pavel Stehule.\n\nBTW: the particular case of IndexScan didn't cause visible duplication\nin a plain EXPLAIN, only EXPLAIN ANALYZE, because in the former case we\nshort-circuit executor startup before the indxqual field is processed by\nExecInitExpr.  That seems like it could easily lead to other EXPLAIN\nproblems in future, but it's not clear how to avoid it without breaking\nthe \"EXPLAIN a plan using hypothetical indexes\" use-case.  For now I've\nleft that issue alone.\n\nAlthough this is a longstanding bug, it's purely cosmetic (no great harm\nis done by the repeat printout) and we haven't had field complaints before.\nSo I'm hesitant to back-patch it, especially since there is some small risk\nof ABI problems due to the need to add a new field to ExplainState.\n\nIn passing, rearrange order of fields in ExplainState to be less random,\nand update some obsolete comments about when/where to initialize them.\n\nReport: <CAFj8pRAimq+NK-menjt+3J4-LFoodDD8Or6=Lc_stcFD+eD4DA@mail.gmail.com>","distinct":true,"url":"https://api.github.com/repos/glukhovn/postgres/commits/4d042999f94a4bc41b86baca5920cd4829e16895"},{"sha":"d3fbd5929ce5cb7468635aac30c2abf02b7d474a","author":{"name":"Peter Eisentraut","email":"2f47089682e4afbd5de3eea4edffc95dfc1eb9de@gmx.net"},"message":"doc: Fix typo\n\nFrom: Alexander Law <exclusion@gmail.com>","distinct":true,"url":"https://api.github.com/repos/glukhovn/postgres/commits/d3fbd5929ce5cb7468635aac30c2abf02b7d474a"},{"sha":"baebab3ace480477f210dadc4633d8d119dfa978","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Allow IMPORT FOREIGN SCHEMA within pl/pgsql.\n\nSince IMPORT FOREIGN SCHEMA has an INTO clause, pl/pgsql needs to be\naware of that and avoid capturing the INTO as an INTO-variables clause.\nThis isn't hard, though it's annoying to have to make IMPORT a plpgsql\nkeyword just for this.  (Fortunately, we have the infrastructure now\nto make it an unreserved keyword, so at least this shouldn't break any\nexisting pl/pgsql code.)\n\nPer report from Merlin Moncure.  Back-patch to 9.5 where IMPORT FOREIGN\nSCHEMA was introduced.\n\nReport: <CAHyXU0wpHf2bbtKGL1gtUEFATCY86r=VKxfcACVcTMQ70mCyig@mail.gmail.com>","distinct":true,"url":"https://api.github.com/repos/glukhovn/postgres/commits/baebab3ace480477f210dadc4633d8d119dfa978"},{"sha":"b9fc9f7c3c4096aca69261af305c679ffe74c32b","author":{"name":"Peter Eisentraut","email":"2f47089682e4afbd5de3eea4edffc95dfc1eb9de@gmx.net"},"message":"Put some things in a better order in psql help","distinct":true,"url":"https://api.github.com/repos/glukhovn/postgres/commits/b9fc9f7c3c4096aca69261af305c679ffe74c32b"},{"sha":"5d4050064bf3f2be056a4a887ec11aa14d0d2562","author":{"name":"Peter Eisentraut","email":"2f47089682e4afbd5de3eea4edffc95dfc1eb9de@gmx.net"},"message":"Add serial comma and quoting to message","distinct":true,"url":"https://api.github.com/repos/glukhovn/postgres/commits/5d4050064bf3f2be056a4a887ec11aa14d0d2562"},{"sha":"42ec6c2da699e8e0b1774988fa97297a2cdf716c","author":{"name":"Stephen Frost","email":"2063edcf0aa2fa8dfb7bba729d6cffa6fed14981@snowman.net"},"message":"Add missing hyphen\n\nPointed out by Alexander Law","distinct":true,"url":"https://api.github.com/repos/glukhovn/postgres/commits/42ec6c2da699e8e0b1774988fa97297a2cdf716c"},{"sha":"91c0eb5040cde36a62a34e9b3a80d82db64eb98f","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Fix obsolete header-file reference in pg_buffercache docs.\n\nCommit 2d0019049 moved enum ForkNumber from relfilenode.h into relpath.h,\nbut missed updating this documentation reference.\n\nAlexander Law","distinct":true,"url":"https://api.github.com/repos/glukhovn/postgres/commits/91c0eb5040cde36a62a34e9b3a80d82db64eb98f"},{"sha":"cec55013943d160538334ee19ef5db429a085969","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Add a regression test case to improve code coverage for tuplesort.\n\nTest the external-sort code path in CLUSTER for two different scenarios:\nmultiple-pass external sorting, and the best case for replacement\nselection, where only one run is produced, so that no merge is required.\nThis test would have caught the bug fixed in commit 1b0fc8507, at\nleast when run with valgrind enabled.\n\nIn passing, add a short-circuit test in plan_cluster_use_sort() to make\ndead certain that it selects sorting when enable_indexscan is off.  As\nthings stand, that would happen anyway, but it seems like good future\nproofing for this test.\n\nPeter Geoghegan\n\nDiscussion: <CAM3SWZSgxehDkDMq1FdiW2A0Dxc79wH0hz1x-TnGy=1BXEL+nw@mail.gmail.com>","distinct":true,"url":"https://api.github.com/repos/glukhovn/postgres/commits/cec55013943d160538334ee19ef5db429a085969"},{"sha":"56a997413391337f7fb9926144d6b6fa831b9d22","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Minor test adjustment.\n\nDept of second thoughts: given the RESET SESSION AUTHORIZATION that\nwas just added by commit cec550139, we don't need the reconnection\nthat used to be here.  Might as well buy back a few microseconds.","distinct":true,"url":"https://api.github.com/repos/glukhovn/postgres/commits/56a997413391337f7fb9926144d6b6fa831b9d22"}]}
{"actor":{"display_login":"glukhovn"}}