{"push_id":2574925477,"size":200,"distinct_size":200,"ref":"refs/heads/master","head":"9effb63e0dd12b0704cd8e11106fe08ff5c9d685","before":"3a2d6365984d2cd98ee03467cd901785941cf772","commits":[{"sha":"158b7bc6d77948d2f474dc9f2777c87f81d1365a","author":{"name":"Alvaro Herrera","email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org"},"message":"Ignore whole-rows in INSERT/CONFLICT with partitioned tables\n\nWe had an Assert() preventing whole-row expressions from being used in\nthe SET clause of INSERT ON CONFLICT, but it seems unnecessary, given\nsome tests, so remove it.  Add a new test to exercise the case.\n\nStill at ExecInitPartitionInfo, we used map_partition_varattnos (which\nconstructs an attribute map, then calls map_variable_attnos) using\nthe same two relations many times in different expressions and with\ndifferent parameters.  Constructing the map over and over is a waste.\nTo avoid this repeated work, construct the map once, and use\nmap_variable_attnos() directly instead.\n\nAuthor: Amit Langote, per comments by me (Álvaro)\nDiscussion: https://postgr.es/m/20180326142016.m4st5e34chrzrknk@alvherre.pgsql","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/158b7bc6d77948d2f474dc9f2777c87f81d1365a"},{"sha":"22ff2b8583b2580d8b423939a658fcd1d38741b4","author":{"name":"Alvaro Herrera","email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org"},"message":"Update expected output of new test\n\nForgot to 'git add' the file after tweaking the test as submitted :-(\n\nPer buildfarm","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/22ff2b8583b2580d8b423939a658fcd1d38741b4"},{"sha":"b15e8f71dbf00eb18d9076302f39aa981355eb07","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Fix broken collation-aware searches in SP-GiST text opclass.\n\nspg_text_leaf_consistent() supposed that it should compare only\nMin(querylen, entrylen) bytes of the two strings, and then deal with\nany excess bytes in one string or the other by assuming the longer\nstring is greater if the prefixes are equal.  Quite aside from the\nfact that that's just wrong in some locales (e.g., 'ch' is not less\nthan 'd' in cs_CZ), it also risked passing incomplete multibyte\ncharacters to strcoll(), with ensuing bad results.\n\nInstead, just pass the full strings to varstr_cmp, and let it decide\nwhat to do about unequal-length strings.\n\nFortunately, this error doesn't imply any index corruption, it's just\nthat searches might return the wrong set of entries.\n\nPer report from Emre Hasegeli, though this is not his patch.\nThanks to Peter Geoghegan for review and discussion.\n\nThis code was born broken, so back-patch to all supported branches.\nIn HEAD, I failed to resist the temptation to do a bit of cosmetic\ncleanup/pgindent'ing on 710d90da1, too.\n\nDiscussion: https://postgr.es/m/CAE2gYzzb6K51VnTq5i5p52z+j9p2duEa-K1T3RrC_GQEynAKEg@mail.gmail.com","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/b15e8f71dbf00eb18d9076302f39aa981355eb07"},{"sha":"47c91b55991883322fdbc4495ce7fe6b2166e8fe","author":{"name":"Alvaro Herrera","email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org"},"message":"Restore partition_prune's usage of parallel workers\n\nThis reverts commit 4d0f6d3f207d (\"Attempt to stabilize partition_prune\ntest output (2)\"), and attempts to stabilize the test by using string\nreplacement to hide any loop count difference in parallel nodes.\n\nDiscussion: https://postgr.es/m/4475.1523628300@sss.pgh.pa.us","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/47c91b55991883322fdbc4495ce7fe6b2166e8fe"},{"sha":"03030512d1e4df78dc2543d3fe3b6d13e5cb63f6","author":{"name":"Tatsuo Ishii","email":"d65e86e9f63e8ebd237ae089e7c4417e05d5f9dd@postgresql.org"},"message":"Add more infinite recursion detection while locking a view.\n\nAlso add regression test cases for detecting infinite recursion in\nlocking view tests.  Some document enhancements. Patch by Yugo Nagata.","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/03030512d1e4df78dc2543d3fe3b6d13e5cb63f6"},{"sha":"95cdc77b35ece28137b8dec8c6f9b5474b215624","author":{"name":"Alvaro Herrera","email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org"},"message":"Improve coverage of nodeAppend runtime partition prune\n\ncoverage report indicated that mark_invalid_subplans_as_finished() and\nnearby code was not getting exercised by any tests.  Add a new one which\nhas execution-time Params rather than only external Params to fix this.\n\nIn passing, David noticed that ab_q6 tests were not actually required to\nhave a generic plan. The tests were testing exec Params not external\nParams, so there was no need for the PREPARE.  Remove the PREPARE,\nmaking these plain queries.  (The new queries are called from\nexplain_parallel_append, which may be unnecessary since they don't\nactually have a Parallel Append node, just an Append.  But it doesn't\nseem to hurt anything, either.)\n\nAuthor: David Rowley\nDiscussion: https://postgr.es/m/CAKJS1f--hopb6JBSDY4wiXTS3ZcDp-wparXjTQ1nzNdBa04Fog@mail.gmail.com","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/95cdc77b35ece28137b8dec8c6f9b5474b215624"},{"sha":"55101549d538c9ed86e761dba0775025726d7310","author":{"name":"Heikki Linnakangas","email":"ac1e0af1ee8efe15f889b38482e897ff7d0f0432@iki.fi"},"message":"Fix a few typos in comments and variable names.\n\nAuthor: Michael Paquier\nDiscussion: https://www.postgresql.org/message-id/20180411075223.GB19732%40paquier.xyz","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/55101549d538c9ed86e761dba0775025726d7310"},{"sha":"b7e2cbc5b49fbab5bc286b9e4cd4062a6703e7a7","author":{"name":"Alvaro Herrera","email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org"},"message":"Update Append's idea of first_partial_plan\n\nIt turns out that after runtime partition pruning, Append's\nfirst_partial_plan does not accurately represent partial plans to run,\nif any of those got pruned.  This could limit participation of workers\nin some partial subplans, if other subplans got pruned.  Fix it by\nkeeping an index of the first valid partial subplan in the state node,\ndetermined at execnode Init time.\n\nAuthor: David Rowley, with cosmetic changes by me.\nDiscussion: https://postgr.es/m/CAKJS1f8o2Yd=rOP=Et3A0FWgF+gSAOkFSU6eNhnGzTPV7nN8sQ@mail.gmail.com","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/b7e2cbc5b49fbab5bc286b9e4cd4062a6703e7a7"},{"sha":"cf5a1890592bfa2f45d306789533efba97496233","author":{"name":"Heikki Linnakangas","email":"ac1e0af1ee8efe15f889b38482e897ff7d0f0432@iki.fi"},"message":"Fix confusion on the padding of GIDs in on commit and abort records.\n\nReview of commit 1eb6d652: It's pointless to add padding to the GID fields,\nwhen the code that follows assumes that there is no alignment, and uses\nmemcpy(). Remove the pointless padding.\n\nUpdate comments to note the new fields in the WAL records.\n\nReviewed-by: Michael Paquier\nDiscussion: https://www.postgresql.org/message-id/33b787bf-dc20-1161-54e9-3f3b607bf59d%40iki.fi","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/cf5a1890592bfa2f45d306789533efba97496233"},{"sha":"e90d4ddc639aac7a7217ebc670ad6e49eaeddbf9","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Simplify genbki.pl's data quoting rules.\n\nDuring the bootstrap data format conversion, it seemed important for\nverifiability's sake that the generated postgres.bki file stayed the same\nas before.  That resulted in adding a bunch of ad-hoc rules about when to\nquote emitted data values, to match previous manual decisions that had\noften quoted values unnecessarily.  Now that the conversion is complete,\nit seems fine to remove all those ad-hoc rules.  The net actual effect on\nthe current contents of postgres.bki is that some fields that had been\nquoted despite containing only digits or only \"-\" lose their unnecessary\nquotes.\n\nAlso, now that genbki.pl will always quote values containing a backslash,\nthere's no need for bootscanner.l to allow unquoted octal escapes;\nso simplify its production for \"id\" by removing that possibility.\n\nJohn Naylor, slightly modified by me\n\nDiscussion: https://postgr.es/m/CAJVSVGUNao=-Q2-vAN3PYcdF5tnL5JAHwGwzZGuYHtq+Mk_9ng@mail.gmail.com","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/e90d4ddc639aac7a7217ebc670ad6e49eaeddbf9"},{"sha":"9ffcccdb958d38db5051bf64143330ff445a26cc","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Rationalize handling of array type names in bootstrap data.\n\nFormerly, Catalog.pm turned a C array type declaration in the catalog\nheader files into a SQL type, e.g., 'foo[]'.  Along the way, genbki.pl\nturned this into '_foo' for the purpose of type lookups, but wrote 'foo[]'\nto postgres.bki.  During bootstrap, bootscanner.l had to have a special\ncase rule to tokenize this, and then MapArrayTypeName() would turn 'foo[]'\ninto '_foo' one more time.\n\nThis seems unnecessarily complicated, especially since nobody cares that\nmuch about the readability of postgres.bki.  Instead, make Catalog.pm\nconvert the C declaration into '_foo' to start with, and preserve that\nrepresentation of the type name throughout bootstrap data processing.\nThen rip out the special-case code in bootscanner.l and bootstrap.c.\n\nThis changes postgres.bki to the extent that array fields are now\ndeclared like\n  proconfig = _text ,\nrather than\n  proconfig = text[] ,\n\nNo documentation update, since the SGML docs didn't mention any of this\nin the first place, and it's all pretty transparent to writers of\ncatalog header files anyway.\n\nJohn Naylor\n\nDiscussion: https://postgr.es/m/CAJVSVGUNao=-Q2-vAN3PYcdF5tnL5JAHwGwzZGuYHtq+Mk_9ng@mail.gmail.com","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/9ffcccdb958d38db5051bf64143330ff445a26cc"},{"sha":"55d26ff638f063fbccf57843f2c27f9795895a5c","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Rationalize handling of single and double quotes in bootstrap data.\n\nChange things around so that proper quoting of values interpolated into\nthe BKI data by initdb is the responsibility of initdb, not something\nwe half-heartedly handle by putting double quotes into the raw BKI data.\n(Note: experimentation shows that it still doesn't work to put a double\nquote into the initial superuser username, but that's the fault of\ninadequate quoting while interpolating the name into SQL scripts;\nthe BKI aspect of it works fine now.)\n\nHaving done that, we can remove the special-case handling of values\nthat look like \"something\" from genbki.pl, and instead teach it to\nescape double --- and single --- quotes properly.  This removes the\nnowhere-documented need to treat those specially in the BKI source\ndata; whatever you write will be passed through unchanged into the\ninserted data value, modulo Perl's rules about single-quoted strings.\n\nAdd documentation explaining the (pre-existing) handling of backslashes\nin the BKI data.\n\nPer an earlier discussion with John Naylor.\n\nDiscussion: https://postgr.es/m/CAJVSVGUNao=-Q2-vAN3PYcdF5tnL5JAHwGwzZGuYHtq+Mk_9ng@mail.gmail.com","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/55d26ff638f063fbccf57843f2c27f9795895a5c"},{"sha":"fe7fc52645678ecb661fde47fe5937b48093f79e","author":{"name":"Heikki Linnakangas","email":"ac1e0af1ee8efe15f889b38482e897ff7d0f0432@iki.fi"},"message":"Improve docs for the new INCLUDE directive in CREATE/ALTER TABLE.\n\nAuthor: Michael Paquier\nDiscussion: https://www.postgresql.org/message-id/20180411082020.GD19732%40paquier.xyz","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/fe7fc52645678ecb661fde47fe5937b48093f79e"},{"sha":"1dec82068b3b59b621e6b04040c150241f5060f3","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Better fix for deadlock hazard in CREATE INDEX CONCURRENTLY.\n\nCommit 54eff5311 did not account for the possibility that we'd have\na transaction snapshot due to default_transaction_isolation being\nset high enough to require one.  The transaction snapshot is enough\nto hold back our advertised xmin and thus risk deadlock anyway.\nThe only way to get rid of that snap is to start a new transaction,\nso let's do that instead.  Also throw in an assert checking that we\nreally have gotten to a state where no xmin is being advertised.\n\nBack-patch to 9.4, like the previous commit.\n\nDiscussion: https://postgr.es/m/CAMkU=1ztk3TpQdcUNbxq93pc80FrXUjpDWLGMeVBDx71GHNwZQ@mail.gmail.com","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/1dec82068b3b59b621e6b04040c150241f5060f3"},{"sha":"5372c2c84135be99e8df921ff228df6e7b4d3c8d","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Improve error detection/reporting in Catalog.pm and genbki.pl.\n\nClean up error messages relating to mistakes in .dat files: make sure they\nprovide the .dat file name and line number, not the place in the Perl\nscript that's reporting the problem.  Adopt more uniform message phrasing,\ntoo.\n\nMake genbki.pl spit up on unrecognized field names in the input hashes.\nPreviously, it just silently ignored such fields, which could make a\nmisspelled field name into a very hard-to-decipher problem.  (This is in\ngenbki.pl, *not* Catalog.pm, because we don't want reformat_dat_file.pl to\ncomplain about unrecognized fields.  We'd rather it silently dropped them,\nto facilitate removing unwanted fields after a reorganization.)","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/5372c2c84135be99e8df921ff228df6e7b4d3c8d"},{"sha":"075aade4361b9f973172b925ddfb908a012b5796","author":{"name":"Teodor Sigaev","email":"231337598724646720571a00c656f975fff6a8f2@sigaev.ru"},"message":"Adjust INCLUDE index truncation comments and code.\n\nAdd several assertions that ensure that we're dealing with a pivot tuple\nwithout non-key attributes where that's expected.  Also, remove the\nassertion within _bt_isequal(), restoring the v10 function signature.  A\nsimilar check will be performed for the page highkey within\n_bt_moveright() in most cases.  Also avoid dropping all objects within\nregression tests, to increase pg_dump test coverage for INCLUDE indexes.\n\nRather than using infrastructure that's generally intended to be used\nwith reference counted heap tuple descriptors during truncation, use the\nsame function that was introduced to store flat TupleDescs in shared\nmemory (we use a temp palloc'd buffer).  This isn't strictly necessary,\nbut seems more future-proof than the old approach.  It also lets us\navoid including rel.h within indextuple.c, which was arguably a\nmodularity violation.  Also, we now call index_deform_tuple() with the\ntruncated TupleDesc, not the source TupleDesc, since that's more robust,\nand saves a few cycles.\n\nIn passing, fix a memory leak by pfree'ing truncated pivot tuple memory\nduring CREATE INDEX.  Also pfree during a page split, just to be\nconsistent.\n\nRefactor _bt_check_natts() to be more readable.\n\nAuthor: Peter Geoghegan with some editorization by me\nReviewed by: Alexander Korotkov, Teodor Sigaev\nDiscussion: https://www.postgresql.org/message-id/CAH2-Wz%3DkCWuXeMrBCopC-tFs3FbiVxQNjjgNKdG2sHxZ5k2y3w%40mail.gmail.com","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/075aade4361b9f973172b925ddfb908a012b5796"},{"sha":"3d927961ae1232487796bebb254d92fb6d0d1e03","author":{"name":"Teodor Sigaev","email":"231337598724646720571a00c656f975fff6a8f2@sigaev.ru"},"message":"Handle XLOG_BTREE_META_CLEANUP in btree_desc() and btree_identify()\n\nNew WAL record XLOG_BTREE_META_CLEANUP introduced in 857f9c36 has no handling\nin btree_desc() and btree_identify().  This patch implements corresponding\nhandling.\n\nAlexander Korotkov","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/3d927961ae1232487796bebb254d92fb6d0d1e03"},{"sha":"f97f0c921ae56bb16e466f3c9d6c504f4a96a539","author":{"name":"Teodor Sigaev","email":"231337598724646720571a00c656f975fff6a8f2@sigaev.ru"},"message":"Adjust _bt_insertonpg() comments\n\nRemove an obsolete reference to the 'afteritem' argument, which was\nremoved by commit bc292937.  Add a comment that clarifies how\n_bt_insertonpg() indirectly handles the insertion of high key items.\n\nAuthor: Peter Geoghegan","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/f97f0c921ae56bb16e466f3c9d6c504f4a96a539"},{"sha":"ff4943042f9761fb4e84432da563f43eb3559a3b","author":{"name":"Teodor Sigaev","email":"231337598724646720571a00c656f975fff6a8f2@sigaev.ru"},"message":"Fix datatype for number of heap tuples during last cleanup\n\nIt appears that new fields introduced in 857f9c36 have inconsistent datatypes:\nBTMetaPageData.btm_last_cleanup_num_heap_tuples is of float4 type,\nwhile xl_btree_metadata.last_cleanup_num_heap_tuples is of double type.\nIndexVacuumInfo.num_heap_tuples, which is a source of values for\nboth former fields is of double type.  So, make both those fields in\nBTMetaPageData and xl_btree_metadata use float8 type in order to match the\nprecision of the source.  That shouldn't be double type, because we always\nuse types with explicit width in WAL.\n\nPatch introduces incompatibility of on-disk format since 857f9c36 commit, but\nthat versions never was released, so just bump catalog version to avoid\npossible confusion.\n\nAuthor: Alexander Korortkov","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/ff4943042f9761fb4e84432da563f43eb3559a3b"},{"sha":"cea5f9aa1244a6a803481f7e21a86e7e7037a9a5","author":{"name":"Alvaro Herrera","email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org"},"message":"Enlarge find_other_exec's meager fgets buffer\n\nThe buffer was 100 bytes long, which is barely sufficient when the\nversion string gets longer (such as by configure --with-extra-version).\nSet it to MAXPGPATH.\n\nAuthor: Nikhil Sontakke\nDiscussion: https://postgr.es/m/CAMGcDxfLfpYU_Jru++L6ARPCOyxr0W+2O3Q54TDi5XdYeU36ow@mail.gmail.com","distinct":true,"url":"https://api.github.com/repos/Algunenano/postgres/commits/cea5f9aa1244a6a803481f7e21a86e7e7037a9a5"}]}
{"actor":{"display_login":"Algunenano"}}