{"push_id":2332808230,"size":4,"distinct_size":1,"ref":"refs/heads/commitfest/17/1464","head":"7cc991106c39e4e62f672fb0ea7b3aa429d4eb7d","before":"67abc9cb8faff30eba430123ab9f7008ca6b9df2","commits":[{"sha":"feb1cc5593a5188796c2f52241f407500209fff2","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Stabilize new plpgsql_record regression tests.\n\nThe buildfarm's CLOBBER_CACHE_ALWAYS animals aren't happy with some\nof the test cases added in commit 4b93f5799.  There are two different\nproblems:\n\n* In two places, a different CONTEXT stack is shown because the error\nis detected in a different place, due to recompiling an expression\nfrom scratch rather than re-using a previously cached plan for it.\nI fixed these via the expedient of hiding the CONTEXT stack altogether.\n\n* In one place, a test expected to fail (because a cached plan hadn't\nbeen updated) actually succeeds (because the forced recompile makes\nit good).  I couldn't think of a simple workaround for this, so I've\njust commented out that test step altogether.\n\nI have hopes of improving things enough that both of these kluges can\nbe reverted eventually.  The first one is the same kind of problem\npreviously discussed at\nhttps://postgr.es/m/31545.1512924904@sss.pgh.pa.us\nbut there was insufficient agreement about how to fix it, so we\njust hacked around the output instability (commit 9edc97b71).\nThe second issue should be fixed by allowing the plan to be rebuilt\nwhen a type conflict is detected.  But for today, let's just make the\nbuildfarm green again.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/feb1cc5593a5188796c2f52241f407500209fff2"},{"sha":"cbadba8dd632fc0d4162f7d686fec631bce7dfd0","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Revert \"Stabilize output of new regression test case\".\n\nThis effectively reverts commit 9edc97b71 (although the test is now\nin a different place and has different contents).  We don't need that\nhack anymore, because since commit 4b93f5799, this test case no longer\nthrows an error and so there's no displayed CONTEXT that could vary\ndepending on CLOBBER_CACHE_ALWAYS.  The underlying unstable-output\nproblem isn't really gone, of course, but it no longer manifests here.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/cbadba8dd632fc0d4162f7d686fec631bce7dfd0"},{"sha":"03c5a00ea3867f5736da6cedce73b1eea88a98af","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Move the extern declaration for ExceptionalCondition into c.h.\n\nThis is the logical conclusion of our decision to support Assert()\nin both frontend and backend code: it should be possible to use that\nafter including just c.h.  But as things were arranged before, if\nyou wanted to use Assert() in code that might be compiled for either\nenvironment, you had to include postgres.h for the backend case.\nLet's simplify that.\n\nPer buildfarm, some of whose members started throwing warnings after\ncommit 0c62356cc added an Assert in src/port/snprintf.c.\n\nIt's possible that some other src/port files that use the stanza\n\n#ifndef FRONTEND\n#include \"postgres.h\"\n#else\n#include \"postgres_fe.h\"\n#endif\n\ncould now be simplified to just say '#include \"c.h\"'.  I have not\ntested for that, though, and it'd be unlikely to apply for more\nthan a small number of them.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/03c5a00ea3867f5736da6cedce73b1eea88a98af"},{"sha":"7cc991106c39e4e62f672fb0ea7b3aa429d4eb7d","author":{"name":"Commitfest Bot","email":"aab6a594935fe5db0d690bc154b19f642bfbe9d7@cputube.org"},"message":"[CF 17/1464] foreign keys and partitioned tables\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 or the master branch changes.\n\nCommitfest entry: https://commitfest.postgresql.org/17/1464\nPatch(es): https://www.postgresql.org/message-id/20180124175245.hsakxldr4cd74svv%40alvherre.pgsql\nAuthor(s): Álvaro Herrera","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/7cc991106c39e4e62f672fb0ea7b3aa429d4eb7d"}]}
{"actor":{"display_login":"postgresql-cfbot"}}