{"push_id":2852678773,"size":6,"distinct_size":1,"ref":"refs/heads/commitfest/19/1755","head":"0d452f0a81bdb82276f46fc2a76b9efb2acf78c7","before":"555ca06b6a0a634ab18467c5dc03feeaca7dd23e","commits":[{"sha":"f30c6f523f9caa73c9ba6ebd82c8d29fe45866a3","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Clean up after TAP tests in oid2name and vacuumlo.\n\nOversights in commits 1aaf532de and bfea331a5.  Unlike the case for\ntraditional-style REGRESS tests, pgxs.mk doesn't have any builtin support\nfor TAP tests, so it doesn't realize it should remove tmp_check/.\nMaybe we should build some actual pgxs infrastructure for TAP tests ...\nbut for the moment, just remove explicitly.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/f30c6f523f9caa73c9ba6ebd82c8d29fe45866a3"},{"sha":"17b7c302b5fc92bd0241c452599019e18df074dc","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Fully enforce uniqueness of constraint names.\n\nIt's been true for a long time that we expect names of table and domain\nconstraints to be unique among the constraints of that table or domain.\nHowever, the enforcement of that has been pretty haphazard, and it missed\nsome corner cases such as creating a CHECK constraint and then an index\nconstraint of the same name (as per recent report from André Hänsel).\nAlso, due to the lack of an actual unique index enforcing this, duplicates\ncould be created through race conditions.\n\nMoreover, the code that searches pg_constraint has been quite inconsistent\nabout how to handle duplicate names if one did occur: some places checked\nand threw errors if there was more than one match, while others just\nprocessed the first match they came to.\n\nTo fix, create a unique index on (conrelid, contypid, conname).  Since\neither conrelid or contypid is zero, this will separately enforce\nuniqueness of constraint names among constraints of any one table and any\none domain.  (If we ever implement SQL assertions, and put them into this\ncatalog, more thought might be needed.  But it'd be at least as reasonable\nto put them into a new catalog; having overloaded this one catalog with\ntwo kinds of constraints was a mistake already IMO.)  This index can replace\nthe existing non-unique index on conrelid, though we need to keep the one\non contypid for query performance reasons.\n\nHaving done that, we can simplify the logic in various places that either\ncoped with duplicates or neglected to, as well as potentially improve\nlookup performance when searching for a constraint by name.\n\nAlso, as per our usual practice, install a preliminary check so that you\nget something more friendly than a unique-index violation report in the\ncase complained of by André.  And teach ChooseIndexName to avoid choosing\nautogenerated names that would draw such a failure.\n\nWhile it's not possible to make such a change in the back branches,\nit doesn't seem quite too late to put this into v11, so do so.\n\nDiscussion: https://postgr.es/m/0c1001d4428f$0942b430$1bc81c90$@webkr.de","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/17b7c302b5fc92bd0241c452599019e18df074dc"},{"sha":"d6e98ebe375e115c29028f9bd090f0f7e07e2527","author":{"name":"Michael Paquier","email":"17b9e1c64588c7fa6419b4d29dc1f4426279ba01@paquier.xyz"},"message":"Improve some error message strings and errcodes\n\nThis makes a bit less work for translators, by unifying error strings a\nbit more with what the rest of the code does, this time for three error\nstrings in autoprewarm and one in base backup code.\n\nAfter some code review of slot.c, some file-access errcodes are reported\nbut lead to an incorrect internal error, while corrupted data makes the\nmost sense, similarly to the previous work done in e41d0a1.  Also,\nafter calling rmtree(), a WARNING gets reported, which is a duplicate of\nwhat the internal call report, so make the code more consistent with all\nother code paths calling this function.\n\nAuthor: Michael Paquier\nDiscussion: https://postgr.es/m/20180902200747.GC1343@paquier.xyz","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/d6e98ebe375e115c29028f9bd090f0f7e07e2527"},{"sha":"dd6073f22a6b5dd6181d8324465dd3c0bf1851e8","author":{"name":"Bruce Momjian","email":"9ae9c44b775ee9b29f4f502415e02e61a9b1a6a0@momjian.us"},"message":"docs:  improve AT TIME ZONE description\n\nThe previous description was unclear.  Also add a third example, change\nuse of time zone acronyms to more verbose descriptions, and add a\nmention that using 'time' with AT TIME ZONE uses the current time zone\nrules.\n\nBackpatch-through: 9.3","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/dd6073f22a6b5dd6181d8324465dd3c0bf1851e8"},{"sha":"f5a6509bb1ec5222a707205941a40f280f3e6e15","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"PL/Python: Remove use of simple slicing API\n\nThe simple slicing API (sq_slice, sq_ass_slice) has been deprecated\nsince Python 2.0 and has been removed altogether in Python 3, so remove\nthose functions from the PLyResult class.  Instead, the non-slice\nmapping functions mp_subscript and mp_ass_subscript can take slice\nobjects as an index.  Since we just pass the index through to the\nunderlying list object, we already support that.  Test coverage was\nalready in place.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/f5a6509bb1ec5222a707205941a40f280f3e6e15"},{"sha":"0d452f0a81bdb82276f46fc2a76b9efb2acf78c7","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 19/1755] Tid scan improvements (ordering and range scan)\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/1755\nPatch(es): https://www.postgresql.org/message-id/CAMyN-kB-nFTkF=VA_JPwFNo08S0d-Yk0F741S2B7LDmYAi8eyA@mail.gmail.com\nAuthor(s): Edmund Horner","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/0d452f0a81bdb82276f46fc2a76b9efb2acf78c7"}]}
{"actor":{"display_login":"postgresql-cfbot"}}