{"push_id":2897771151,"size":13,"distinct_size":1,"ref":"refs/heads/commitfest/19/1296","head":"f21103bf55f12fc7bad9e54b7a71759cf4eb0e58","before":"d214263f8d62f622e0562bd3a018795a05e179ec","commits":[{"sha":"3dc820c43e427371b66d217f2bd5481fc9ef2e2d","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Teach genbki.pl to auto-generate pg_type entries for array types.\n\nThis eliminates some more tedium in adding new catalog entries,\nspecifically the need to set up an array type when adding a new\nbuilt-in data type.  Now it's sufficient to assign an OID for the\narray type and write it in an \"array_type_oid\" metadata field.\nYou don't have to fill the base type's typarray link explicitly, either.\n\nNo catversion bump since the contents of pg_type aren't changed.\n(Well, their order might be different, but that doesn't matter.)\n\nJohn Naylor, reviewed and whacked around a bit by\nDagfinn Ilmari Mannsåker, and some more by me.\n\nDiscussion: https://postgr.es/m/CAJVSVGVTb6m9pJF49b3SuA8J+T-THO9c0hxOmoyv-yGKh-FbNg@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/3dc820c43e427371b66d217f2bd5481fc9ef2e2d"},{"sha":"b09a64d602a19c9a3cc69e4bb0f8986a6f5facf4","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Add missing pg_description strings for pg_type entries.\n\nI noticed that all non-composite, non-array entries in pg_type.dat\nhad descr strings, except for \"json\" and the pseudo-types.  The\nlack for json seems certainly an oversight, and there's surely\nlittle reason to not have entries for the pseudo-types either.\nSo add some.\n\n\"make reformat-dat-files\" turned up some formatting issues in\npg_amop.dat, too, so fix those in passing.\n\nNo catversion bump since the backend doesn't care too much what is\nin pg_description.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/b09a64d602a19c9a3cc69e4bb0f8986a6f5facf4"},{"sha":"1dba1b61c2fbe0164453963d51e7b0f6c49d8fca","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Add a \"return\" statement to pacify perlcritic.\n\nPer buildfarm member crake.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/1dba1b61c2fbe0164453963d51e7b0f6c49d8fca"},{"sha":"a7c4dad1a770c1c4256aa87e01a85172e1549aad","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Fix psql's tab completion for ALTER DATABASE ... SET TABLESPACE.\n\nWe have the infrastructure to offer a list of tablespace names, but\nit wasn't being used here; instead you got \"FROM\", \"CURRENT\", and \"TO\"\nwhich aren't actually legal in this syntax.\n\nDagfinn Ilmari Mannsåker, reviewed by Arthur Zakirov\n\nDiscussion: https://postgr.es/m/d8jo9djvm7h.fsf@dalvik.ping.uio.no","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/a7c4dad1a770c1c4256aa87e01a85172e1549aad"},{"sha":"c9a8a401f169ec793b1a89b71b0340dd2cfe8bd7","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Fix psql's tab completion for TABLE.\n\nThis should offer the same relation types that SELECT ... FROM would.\nYou can't select from an index for instance, so offering it here is\nunhelpful.  Noted while testing ilmari's recent patch.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/c9a8a401f169ec793b1a89b71b0340dd2cfe8bd7"},{"sha":"925673f27b1df2d9582f66b33519771137b1df7f","author":{"name":"Michael Paquier","email":"17b9e1c64588c7fa6419b4d29dc1f4426279ba01@paquier.xyz"},"message":"Remove special handling for open() in initdb for Windows\n\n40cfe86 enforces the translation mode to text for all frontends, so this\nspecial handling in initdb is not needed anymore.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/925673f27b1df2d9582f66b33519771137b1df7f"},{"sha":"bd1463e348fcf3a6e832092ccdeaecda2db9c117","author":{"name":"Andres Freund","email":"883768b6dd2c42aea0031b24be8a2da40fef4b64@anarazel.de"},"message":"Error out for clang on x86-32 without SSE2 support, no -fexcess-precision.\n\nAs clang currently doesn't support -fexcess-precision=standard,\ncompiling x86-32 code with SSE2 disabled, can lead to problems with\nfloating point overflow checks and the like.\n\nThis issue was noticed because clang, on at least some BSDs, defaults\nto i386 compatibility, whereas it defaults to pentium4 on Linux.  Our\nforced usage of __builtin_isinf() lead to some overflow checks not\ntriggering when compiling for i386, e.g. when the result of the\ncalculation didn't overflow in 80bit registers, but did so in 64bit.\n\nWhile we could just fall back to a non-builtin isinf, it seems likely\nthat the use of 80bit registers leads to other problems (which is why\nwe force the flag for GCC already).  Therefore error out when\ndetecting clang in that situation.\n\nReported-By: Victor Wagner\nAnalyzed-By: Andrew Gierth and Andres Freund\nAuthor: Andres Freund\nDiscussion: https://postgr.es/m/20180905005130.ewk4xcs5dgyzcy45@alap3.anarazel.de\nBackpatch: 9.3-, all supported versions are affected","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/bd1463e348fcf3a6e832092ccdeaecda2db9c117"},{"sha":"ce9cf8e7e6c436e13a729e2369c2c7ca1eae064d","author":{"name":"Michael Paquier","email":"17b9e1c64588c7fa6419b4d29dc1f4426279ba01@paquier.xyz"},"message":"Document lock taken on referenced table when adding a foreign key\n\nThis can happen for CREATE TABLE and ALTER TABLE, so a mention is added\nto both of them in the concerned subsections.\n\nAuthor: Adrien Nayrat\nDiscussion: https://postgr.es/m/c4e8af11-1dfc-766a-c953-76979b9fcdaa@anayrat.info","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/ce9cf8e7e6c436e13a729e2369c2c7ca1eae064d"},{"sha":"f025bd2ddd07a46560a5fbe8dd4790f153ead705","author":{"name":"Thomas Munro","email":"1ff054ef0838bf068a4b7c40eef026e560a37025@postgresql.org"},"message":"Use size_t consistently in dsa.{ch}.\n\nTakeshi Ideriha complained that there is a mixture of Size and size_t\nin dsa.c and corresponding header.  Let's use size_t.  Back-patch to 10\nwhere dsa.c landed, to make future back-patching easy.\n\nDiscussion: https://postgr.es/m/4E72940DA2BF16479384A86D54D0988A6F19ABD9%40G01JPEXMBKW04","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/f025bd2ddd07a46560a5fbe8dd4790f153ead705"},{"sha":"e3b7a6d165d42b59b2432c415d7e4a284a645e89","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Rationalize Query_for_list_of_[relations] query names in tab-complete.c.\n\nThe previous convention was to use names based on the set of relkinds being\nselected for, which was not at all helpful for maintenance, especially\nsince people had been quite inconsistent about whether to change the names\nwhen they changed the relkinds being selected for.  Instead, use names\nbased on the functionality we need the relation to have, following the\nmodel established by Query_for_list_of_updatables.\n\nWhile at it, sort the list of Query constants a bit better; it had the\ndistinct air of code-assembled-by-dartboard before.\n\nDiscussion: https://postgr.es/m/14830.1537481254@sss.pgh.pa.us","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/e3b7a6d165d42b59b2432c415d7e4a284a645e89"},{"sha":"121213d9d8527f880f153e4a032ee1a4cd43833f","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Improve tab completion for ANALYZE, EXPLAIN, and VACUUM.\n\nPreviously, we made no attempt to provide tab completion in these\nstatements' optional parenthesized options lists.  This patch teaches\npsql to do so.\n\nTo prevent the option completions from being offered after we've already\nseen a complete parenthesized option list, it's necessary to improve\nword_matches() so that it allows a wildcard '*' in the middle of an\nalternative, not only at the end as formerly.  That requires only a\nlittle more code than before, and it allows us to test for \"incomplete\nparenthesized options\" with a test like\n\n    else if (HeadMatches2(\"EXPLAIN\", \"(*\") &&\n             !HeadMatches2(\"EXPLAIN\", \"(*)\"))\n\nIn addition, add some logic to offer column names in the context of\n\"ANALYZE tablename ( ...\", and likewise for VACUUM.  This isn't real\ncomplete; it won't offer column names again after a comma.  But it's\nbetter than before, and it doesn't take much code.\n\nJustin Pryzby, reviewed at various times by Álvaro Herrera, Arthur\nZakirov, and Edmund Horner; some additional fixups by me\n\nDiscussion: https://postgr.es/m/20180529000623.GA21896@telsasoft.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/121213d9d8527f880f153e4a032ee1a4cd43833f"},{"sha":"e8fe426baa9c242d8dbd4eab1d963e952c9172f4","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Fix bogus tab-completion rule for CREATE PUBLICATION.\n\nYou can't use \"FOR TABLE\" as a single Matches argument, because readline\nwill consider that input to be two words not one.  It's necessary to make\nthe pattern contain two arguments.\n\nThe case accidentally worked anyway because the words_after_create\ntest fired ... but only for the first such table name.\n\nNoted by Edmund Horner, though this isn't exactly his proposed fix.\nBackpatch to v10 where the faulty code came in.\n\nDiscussion: https://postgr.es/m/CAMyN-kDe=gBmHgxWwUUaXuwK+p+7g1vChR7foPHRDLE592nJPQ@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/e8fe426baa9c242d8dbd4eab1d963e952c9172f4"},{"sha":"f21103bf55f12fc7bad9e54b7a71759cf4eb0e58","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 19/1296] Better estimate for filter cost\n\nThis commit was automatically generated by cfbot at commitfest.cputube.org.\nIt is based on patches submitted to the PostgreSQL mailing lists and\nregistered in the PostgreSQL Commitfest application.\n\nThis branch will be overwritten each time a new patch version is posted to\nthe email thread, and also periodically to check for bitrot caused by changes\non the master branch.\n\nCommitfest entry: https://commitfest.postgresql.org/19/1296\nPatch(es): https://www.postgresql.org/message-id/CANE+7D9CJZc4RsJqq5oC7TptDyVPbrvex618deprGknkgsMqqA@mail.gmail.com\nAuthor(s): Yuto Hayamizu, Ryoji Kawamichi","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/f21103bf55f12fc7bad9e54b7a71759cf4eb0e58"}]}
{"actor":{"display_login":"postgresql-cfbot"}}