{"push_id":1251564140,"size":12,"distinct_size":12,"ref":"refs/heads/join_tsconfig","head":"e82f4973efa32c4227622b5727b81a750ede841e","before":"c0b5b41035b017e4d88fb24a4e6587687be3ff1f","commits":[{"sha":"0f249fe5f5cb3c83fd8e05743740b35ff5d34196","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Fix busted Assert for CREATE MATVIEW ... WITH NO DATA.\n\nCommit 874fe3aea changed the command tag returned for CREATE MATVIEW/CREATE\nTABLE AS ... WITH NO DATA, but missed that there was code in spi.c that\nexpected the command tag to always be \"SELECT\".  Fortunately, the\nconsequence was only an Assert failure, so this oversight should have no\nimpact in production builds.\n\nSince this code path was evidently un-exercised, add a regression test.\n\nPer report from Shivam Saxena. Back-patch to 9.3, like the previous commit.\n\nMichael Paquier\n\nReport: <97218716-480B-4527-B5CD-D08D798A0C7B@dresources.com>","distinct":true,"url":"https://api.github.com/repos/select-artur/postgres/commits/0f249fe5f5cb3c83fd8e05743740b35ff5d34196"},{"sha":"e3049285a3b8790e26e584fdf1ca31ea2e2eb4bc","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Trivial cosmetic cleanup in bloom/blutils.c.\n\nDon't spell \"InvalidOid\" as \"0\".  Initialize method fields in the same\norder as amapi.h declares them (and every other AM handler initializes\nthem).","distinct":true,"url":"https://api.github.com/repos/select-artur/postgres/commits/e3049285a3b8790e26e584fdf1ca31ea2e2eb4bc"},{"sha":"371b572df2d7e24750f8d0fc2e45d673ac70beec","author":{"name":"Alvaro Herrera","email":"7cf34a26c111482b1b00703daedc3ff840f1e2cf@alvh.no-ip.org"},"message":"Add ID property to replication slots' sect2","distinct":true,"url":"https://api.github.com/repos/select-artur/postgres/commits/371b572df2d7e24750f8d0fc2e45d673ac70beec"},{"sha":"6e75559ea9cb0bc8fd07543567cd02d4ec85ca20","author":{"name":"Simon Riggs","email":"3a69a7dd305e9c7705028afae27095688d25197a@2ndQuadrant.com"},"message":"Correct TABLESAMPLE docs\n\nOriginal wording was correct but not the intended meaning.\n\nReported by Patrik Wenger","distinct":true,"url":"https://api.github.com/repos/select-artur/postgres/commits/6e75559ea9cb0bc8fd07543567cd02d4ec85ca20"},{"sha":"e05f6f75dbe00a7349dccf1116b5ed983b4728c0","author":{"name":"Simon Riggs","email":"3a69a7dd305e9c7705028afae27095688d25197a@2ndQuadrant.com"},"message":"Code cleanup in SyncRepWaitForLSN()\n\nCommit 14e8803f1 removed LWLocks when accessing MyProc->syncRepState\nbut didn't clean up the surrounding code and comments.\n\nCleanup and backpatch to 9.5, to keep code similar.\n\nJulien Rouhaud, improved by suggestion from Michael Paquier,\nimplemented trivially by myself.","distinct":true,"url":"https://api.github.com/repos/select-artur/postgres/commits/e05f6f75dbe00a7349dccf1116b5ed983b4728c0"},{"sha":"4b234fd8bf21cd6f5ff44f1f1c613bf40860998d","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Fix inappropriate printing of never-measured times in EXPLAIN.\n\nEXPLAIN (ANALYZE, TIMING OFF) would print an elapsed time of zero for\na trigger function, because no measurement has been taken but it printed\nthe field anyway.  This isn't what EXPLAIN does elsewhere, so suppress it.\n\nIn the same vein, EXPLAIN (ANALYZE, BUFFERS) with non-text output format\nwould print buffer I/O timing numbers even when no measurement has been\ntaken because track_io_timing is off.  That seems not per policy, either,\nso change it.\n\nBack-patch to 9.2 where these features were introduced.\n\nMaksim Milyutin\n\nDiscussion: <081c0540-ecaa-bd29-3fd2-6358f3b359a9@postgrespro.ru>","distinct":true,"url":"https://api.github.com/repos/select-artur/postgres/commits/4b234fd8bf21cd6f5ff44f1f1c613bf40860998d"},{"sha":"499787819309293f3d2cd7219aee334a0e7d5069","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Doc: clarify that DROP ... CASCADE is recursive.\n\nApparently that's not obvious to everybody, so let's belabor the point.\n\nIn passing, document that DROP POLICY has CASCADE/RESTRICT options (which\nit does, per gram.y) but they do nothing (I assume, anyway).  Also update\nsome long-obsolete commentary in gram.y.\n\nDiscussion: <20160805104837.1412.84915@wrigleys.postgresql.org>","distinct":true,"url":"https://api.github.com/repos/select-artur/postgres/commits/499787819309293f3d2cd7219aee334a0e7d5069"},{"sha":"ed0097e4f9e6b1227935e01fa67f12a238b66064","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Add SQL-accessible functions for inspecting index AM properties.\n\nPer discussion, we should provide such functions to replace the lost\nability to discover AM properties by inspecting pg_am (cf commit\n65c5fcd35).  The added functionality is also meant to displace any code\nthat was looking directly at pg_index.indoption, since we'd rather not\nbelieve that the bit meanings in that field are part of any client API\ncontract.\n\nAs future-proofing, define the SQL API to not assume that properties that\nare currently AM-wide or index-wide will remain so unless they logically\nmust be; instead, expose them only when inquiring about a specific index\nor even specific index column.  Also provide the ability for an index\nAM to override the behavior.\n\nIn passing, document pg_am.amtype, overlooked in commit 473b93287.\n\nAndrew Gierth, with kibitzing by me and others\n\nDiscussion: <87mvl5on7n.fsf@news-spur.riddles.org.uk>","distinct":true,"url":"https://api.github.com/repos/select-artur/postgres/commits/ed0097e4f9e6b1227935e01fa67f12a238b66064"},{"sha":"d6c9e05cb7db64239887fac65b243229594f331d","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Fix assorted bugs in contrib/bloom.\n\nIn blinsert(), cope with the possibility that a page we pull from the\nnotFullPage list is marked BLOOM_DELETED.  This could happen if VACUUM\nrecently marked it deleted but hasn't (yet) updated the metapage.\nWe can re-use such a page safely, but we *must* reinitialize it so that\nit's no longer marked deleted.\n\nFix blvacuum() so that it updates the notFullPage list even if it's\ngoing to update it to empty.  The previous \"optimization\" of skipping\nthe update seems pretty dubious, since it means that the next blinsert()\nwill uselessly visit whatever pages we left in the list.\n\nUniformly treat PageIsNew pages the same as deleted pages.  This should\nallow proper recovery if a crash occurs just after relation extension.\n\nProperly use vacuum_delay_point, not assorted ad-hoc CHECK_FOR_INTERRUPTS\ncalls, in the blvacuum() main loop.\n\nFix broken tuple-counting logic: blvacuum.c counted the number of live\nindex tuples over again in each scan, leading to VACUUM VERBOSE reporting\nsome multiple of the actual number of surviving index tuples after any\nvacuum that removed any tuples (since they'd be counted in blvacuum, maybe\nmore than once, and then again in blvacuumcleanup, without ever zeroing the\ncounter).  It's sufficient to count them in blvacuumcleanup.\n\nstats->estimated_count is a boolean, not a counter, and we don't want\nto set it true, so don't add tuple counts to it.\n\nAdd a couple of Asserts that we don't overrun available space on a bloom\npage.  I don't think there's any bug there today, but the way the\nFreeBlockNumberArray size calculation is set up is scarily fragile, and\nBloomPageGetFreeSpace isn't much better.  The Asserts should help catch\nany future mistakes.\n\nPer investigation of a report from Jeff Janes.  I think the first item\nabove may explain his report; the other changes were things I noticed\nwhile casting about for an explanation.\n\nReport: <CAMkU=1xEUuBphDwDmB1WjN4+td4kpnEniFaTBxnk1xzHCw8_OQ@mail.gmail.com>","distinct":true,"url":"https://api.github.com/repos/select-artur/postgres/commits/d6c9e05cb7db64239887fac65b243229594f331d"},{"sha":"9389fbd0385776adf3252eb8cfe6e37a640fdff4","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Remove bogus dependencies on NUMERIC_MAX_PRECISION.\n\nNUMERIC_MAX_PRECISION is a purely arbitrary constraint on the precision\nand scale you can write in a numeric typmod.  It might once have had\nsomething to do with the allowed range of a typmod-less numeric value,\nbut at least since 9.1 we've allowed, and documented that we allowed,\nany value that would physically fit in the numeric storage format;\nwhich is something over 100000 decimal digits, not 1000.\n\nHence, get rid of numeric_in()'s use of NUMERIC_MAX_PRECISION as a limit\non the allowed range of the exponent in scientific-format input.  That was\nespecially silly in view of the fact that you can enter larger numbers as\nlong as you don't use 'e' to do it.  Just constrain the value enough to\navoid localized overflow, and let make_result be the final arbiter of what\nis too large.  Likewise adjust ecpg's equivalent of this code.\n\nAlso get rid of numeric_recv()'s use of NUMERIC_MAX_PRECISION to limit the\nnumber of base-NBASE digits it would accept.  That created a dump/restore\nhazard for binary COPY without doing anything useful; the wire-format\nlimit on number of digits (65535) is about as tight as we would want.\n\nIn HEAD, also get rid of pg_size_bytes()'s unnecessary intimacy with what\nthe numeric range limit is.  That code doesn't exist in the back branches.\n\nPer gripe from Aravind Kumar.  Back-patch to all supported branches,\nsince they all contain the documentation claim about allowed range of\nNUMERIC (cf commit cabf5d84b).\n\nDiscussion: <2895.1471195721@sss.pgh.pa.us>","distinct":true,"url":"https://api.github.com/repos/select-artur/postgres/commits/9389fbd0385776adf3252eb8cfe6e37a640fdff4"},{"sha":"55bbaa66a71c7e4b9599bf7612648fc2fed32953","author":{"name":"Artur Zakirov","email":"6dc7c6d86b7b5b9aef19e5cb2593c6845c365fba@postgrespro.ru"},"message":"Merge from master","distinct":true,"url":"https://api.github.com/repos/select-artur/postgres/commits/55bbaa66a71c7e4b9599bf7612648fc2fed32953"},{"sha":"e82f4973efa32c4227622b5727b81a750ede841e","author":{"name":"Artur Zakirov","email":"6dc7c6d86b7b5b9aef19e5cb2593c6845c365fba@postgrespro.ru"},"message":"dict_simple fixes","distinct":true,"url":"https://api.github.com/repos/select-artur/postgres/commits/e82f4973efa32c4227622b5727b81a750ede841e"}]}
{"actor":{"display_login":"select-artur"}}