{"push_id":2874831678,"size":8,"distinct_size":1,"ref":"refs/heads/commitfest/19/1655","head":"4cc35dc00e597d0cd050f28f1049cd90e449237b","before":"d1eea5c023ef8d75ab05b67770dde66df242afb9","commits":[{"sha":"ba37349cff781120f61b2778257f594f0d10253c","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"ecpg: Change --version output to common style\n\nWhen we removed the ecpg-specific versions, we also removed the\n\"(PostgreSQL)\" from the --version output, which we show in other\nprograms.\n\nReported-by: Ioseph Kim <pgsql-kr@postgresql.kr>","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/ba37349cff781120f61b2778257f594f0d10253c"},{"sha":"b7f6bcbffcc0b41d783c0c9c61766428159969ff","author":{"name":"Andrew Gierth","email":"f5e6496b0ff21826a604b558aceee3773835e92d@postgresql.org"},"message":"Repair bug in regexp split performance improvements.\n\nCommit c8ea87e4b introduced a temporary conversion buffer for\nsubstrings extracted during regexp splits. Unfortunately the code that\nsized it was failing to ignore the effects of ignored degenerate\nregexp matches, so for regexp_split_* calls it could under-size the\nbuffer in such cases.\n\nFix, and add some regression test cases (though those will only catch\nthe bug if run in a multibyte encoding).\n\nBackpatch to 9.3 as the faulty code was.\n\nThanks to the PostGIS project, Regina Obe and Paul Ramsey for the\nreport (via IRC) and assistance in analysis. Patch by me.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/b7f6bcbffcc0b41d783c0c9c61766428159969ff"},{"sha":"7046d30246057b65dd7ad735fd89058684e782cd","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Minor fixes for psql tab completion.\n\n* Include partitioned tables in what's offered after ANALYZE.\n\n* Include toast_tuple_target in what's offered after ALTER TABLE ... SET|RESET.\n\n* Include HASH in what's offered after PARTITION BY.\n\nThis is extracted from a larger patch; these bits seem like\nuncontroversial bug fixes for v11 features, so back-patch them into v11.\n\nJustin Pryzby\n\nDiscussion: https://postgr.es/m/20180529000623.GA21896@telsasoft.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/7046d30246057b65dd7ad735fd89058684e782cd"},{"sha":"e5f1bb92cfa724ba50f5b42a9cd3f8ab544b960a","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"Simplify index tuple descriptor initialization\n\nWe have two code paths for initializing the tuple descriptor for a new\nindex: For a normal index, we copy the tuple descriptor from the table\nand reset a number of fields that are not applicable to indexes.  For an\nexpression index, we make a blank tuple descriptor and fill in the\nneeded fields based on the provided expressions.  As pg_attribute has\ngrown over time, the number of fields that we need to reset in the first\ncase is now bigger than the number of fields we actually want to copy,\nso it's sensible to do it the other way around: Make a blank descriptor\nand copy just the fields we need.  This also allows more code sharing\nbetween the two branches, and it avoids having to touch this code for\nalmost every unrelated change to the pg_attribute structure.\n\nReviewed-by: Arthur Zakirov <a.zakirov@postgrespro.ru>","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/e5f1bb92cfa724ba50f5b42a9cd3f8ab544b960a"},{"sha":"514a731ddcd8449d8a7bfb96f138c72c694a7ef8","author":{"name":"Michael Paquier","email":"17b9e1c64588c7fa6419b4d29dc1f4426279ba01@paquier.xyz"},"message":"Simplify static function in extension.c\n\nAn extra argument for the filename defining the extension script\nlocation was present, aimed at being used for error reporting, but has\nnever been used.  This was around since extensions have been added in\nd9572c4.\n\nAuthor: Yugo Nagata\nReviewed-by: Tatsuo Ishii\nDiscussion: https://postgr.es/m/20180907180504.1ff19e1675bb44a67e9c7ab1@sraoss.co.jp","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/514a731ddcd8449d8a7bfb96f138c72c694a7ef8"},{"sha":"bc153c941d2ec4e605b1e79be9478abc3d166a18","author":{"name":"Amit Kapila","email":"4c828daf437d3cc4e3dadceacc8c2924836485c1@postgresql.org"},"message":"Attach FPI to the first record after full_page_writes is turned on.\n\nXLogInsert fails to attach a required FPI to the first record after\nfull_page_writes is turned on by the last checkpoint.  This bug got\nintroduced in 9.5 due to code rearrangement in commits 2c03216d83 and\n2076db2aea.  Fix it by ensuring that XLogInsertRecord performs a\nrecomputation when the given record is generated with FPW as off but\nfound that the flag has been turned on while actually inserting the\nrecord.\n\nReported-by: Kyotaro Horiguchi\nAuthor: Kyotaro Horiguchi\nReviewed-by: Amit Kapila\nBackpatch-through: 9.5 where this problem was introduced\nDiscussion: https://postgr.es/m/20180420.151043.74298611.horiguchi.kyotaro@lab.ntt.co.jp","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/bc153c941d2ec4e605b1e79be9478abc3d166a18"},{"sha":"23bd3cec6eb1ffb80ed2601c13f89d89e658fcc1","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Attempt to identify system timezone by reading /etc/localtime symlink.\n\nOn many modern platforms, /etc/localtime is a symlink to a file within the\nIANA database.  Reading the symlink lets us find out the name of the system\ntimezone directly, without going through the brute-force search embodied in\nscan_available_timezones().  This shortens the runtime of initdb by some\ntens of ms, which is helpful for the buildfarm, and it also allows us to\nreliably select the same zone name the system was actually configured for,\nrather than possibly choosing one of IANA's many zone aliases.  (For\nexample, in a system configured for \"Asia/Tokyo\", the brute-force search\nwould not choose that name but its alias \"Japan\", on the grounds of the\nlatter string being shorter.  More surprisingly, \"Navajo\" is preferred\nto either \"America/Denver\" or \"US/Mountain\", as seen in an old complaint\nfrom Josh Berkus.)\n\nIf /etc/localtime doesn't exist, or isn't a symlink, or we can't make\nsense of its contents, or the contents match a zone we know but that\nzone doesn't match the observed behavior of localtime(), fall back to\nthe brute-force search.\n\nAlso, tweak initdb so that it prints the zone name it selected.\n\nIn passing, replace the last few references to the \"Olson\" database in\ncode comments with \"IANA\", as that's been our preferred term since\ncommit b2cbced9e.\n\nPatch by me, per a suggestion from Robert Haas; review by Michael Paquier\n\nDiscussion: https://postgr.es/m/7408.1525812528@sss.pgh.pa.us","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/23bd3cec6eb1ffb80ed2601c13f89d89e658fcc1"},{"sha":"4cc35dc00e597d0cd050f28f1049cd90e449237b","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 19/1655] Check constraint documentation about cross table constraint\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/1655\nPatch(es): https://www.postgresql.org/message-id/CAB_COdjmb812b23MRDaadWkRN5iBGK1eMP89yD5haDgK_0Usnw@mail.gmail.com\nAuthor(s): Lætitia AVROT, Patrick Francelle","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/4cc35dc00e597d0cd050f28f1049cd90e449237b"}]}
{"actor":{"display_login":"postgresql-cfbot"}}