{"push_id":2898253870,"size":9,"distinct_size":1,"ref":"refs/heads/commitfest/19/1751","head":"dd1c8717e87eabac5b8d02540e0aea4b81a11def","before":"7bba946f09a2619c16af894937a90395ae7582bf","commits":[{"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":"f77de4b0c0ad8c351223929b6fb3ee5c300a9979","author":{"name":"Bruce Momjian","email":"9ae9c44b775ee9b29f4f502415e02e61a9b1a6a0@momjian.us"},"message":"docs:  remove use of escape strings and use bytea hex output\n\nstandard_conforming_strings defaulted to 'on' in PG 9.1.\nbytea_output defaulted to 'hex' in PG 9.0.\n\nReported-by: André Hänsel\n\nDiscussion: https://postgr.es/m/12e601d447ac$345994a0$9d0cbde0$@webkr.de\n\nBackpatch-through: 9.3","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/f77de4b0c0ad8c351223929b6fb3ee5c300a9979"},{"sha":"1f7fc7670c7e0051b47bb4a4d6b41ff9e8af53fa","author":{"name":"Bruce Momjian","email":"9ae9c44b775ee9b29f4f502415e02e61a9b1a6a0@momjian.us"},"message":"doc:  JIT is enabled by default in PG 12\n\nJIT was disabled by default in a PG 11 in a separate commit that will\nnormally not appear in the PG 12 git logs.  Therefore, create a PG 12\ndocument and mention the fact that JIT is enabled by default in this\nrelease.  (A similar change in parallelism was missed in a prior\nrelease.)\n\nReported-by: Andres Freund\n\nDiscussion: https://postgr.es/m/20180922000554.qukbhhlagpnopvko@alap3.anarazel.de\n\nBackpatch-through: head","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/1f7fc7670c7e0051b47bb4a4d6b41ff9e8af53fa"},{"sha":"4f3b38fe2bde72d59b7eab593ff72e0cebd9ecc6","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Get rid of explicit argument-count markings in tab-complete.c.\n\nThis replaces the \"TailMatchesN\" macros with just \"TailMatches\",\nand likewise \"HeadMatchesN\" becomes \"HeadMatches\" and \"MatchesN\"\nbecomes \"Matches\".  The various COMPLETE_WITH_LISTn macros are\nreduced to COMPLETE_WITH, and the single-item COMPLETE_WITH_CONST\nalso gets folded into that.  This eliminates a lot of minor\nannoyance in writing tab-completion rules.  Usefully, the compiled\ncode also gets a bit smaller (10% or so, on my machine).\n\nThe implementation depends on variadic macros, so we couldn't have\ndone this before we required C99.\n\nAndres Freund and Thomas Munro; some cosmetic cleanup by me.\n\nDiscussion: https://postgr.es/m/d8jo9djvm7h.fsf@dalvik.ping.uio.no","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/4f3b38fe2bde72d59b7eab593ff72e0cebd9ecc6"},{"sha":"dd1c8717e87eabac5b8d02540e0aea4b81a11def","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 19/1751] pgbench - set non zero exit code on all errors\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/1751\nPatch(es): https://www.postgresql.org/message-id/260c6cce-ff12-4c78-0c72-bd4a1a738cbd@2ndquadrant.com\nAuthor(s): Peter Eisentraut","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/dd1c8717e87eabac5b8d02540e0aea4b81a11def"}]}
{"actor":{"display_login":"postgresql-cfbot"}}