{"push_id":2805434791,"size":9,"distinct_size":1,"ref":"refs/heads/commitfest/19/1621","head":"00f03118962f32c111e719bd382f3716a353e694","before":"d77844f3483069a7e39652e96e8855a1eb562229","commits":[{"sha":"fa73b377ee11ced0c051fb42c29a87b5c71b79e3","author":{"name":"Tomas Vondra","email":"07d6043e15c7eaaf8513ba9a264e5412dbd73bf7@postgresql.org"},"message":"Close the file descriptor in ApplyLogicalMappingFile\n\nThe function was forgetting to close the file descriptor, resulting\nin failures like this:\n\n  ERROR:  53000: exceeded maxAllocatedDescs (492) while trying to open\n  file \"pg_logical/mappings/map-4000-4eb-1_60DE1E08-5376b5-537c6b\"\n  LOCATION:  OpenTransientFile, fd.c:2161\n\nSimply close the file at the end, and backpatch to 9.4 (where logical\ndecoding was introduced). While at it, fix a nearby typo.\n\nDiscussion: https://www.postgresql.org/message-id/flat/738a590a-2ce5-9394-2bef-7b1caad89b37%402ndquadrant.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/fa73b377ee11ced0c051fb42c29a87b5c71b79e3"},{"sha":"1eb9221585c25cad1a563bc3414f697dae3fbc8b","author":{"name":"Alvaro Herrera","email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org"},"message":"Fix executor prune failure when plan already pruned\n\nIn a multi-layer partitioning setup, if at plan time all the\nsub-partitions are pruned but the intermediate one remains, the executor\nlater throws a spurious error that there's nothing to prune.  That is\ncorrect, but there's no reason to throw an error.  Therefore, don't.\n\nReported-by: Andreas Seltenreich <seltenreich@gmx.de>\nAuthor: David Rowley <david.rowley@2ndquadrant.com>\nDiscussion: https://postgr.es/m/87in4h98i0.fsf@ansel.ydns.eu","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/1eb9221585c25cad1a563bc3414f697dae3fbc8b"},{"sha":"e1d19c902e59ad739cb4b6267ee2073a61e86cd3","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Require a C99-compliant snprintf(), and remove related workarounds.\n\nSince our substitute snprintf now returns a C99-compliant result,\nthere's no need anymore to have complicated code to cope with pre-C99\nbehavior.  We can just make configure substitute snprintf.c if it finds\nthat the system snprintf() is pre-C99.  (Note: I do not believe that\nthere are any platforms where this test will trigger that weren't\nalready being rejected due to our other C99-ish feature requirements for\nsnprintf.  But let's add the check for paranoia's sake.)  Then, simplify\nthe call sites that had logic to cope with the pre-C99 definition.\n\nI also dropped some stuff that was being paranoid about the possibility\nof snprintf overrunning the given buffer.  The only reports we've ever\nheard of that being a problem were for Solaris 7, which is long dead,\nand we've sure not heard any reports of these assertions triggering in\na long time.  So let's drop that complexity too.\n\nLikewise, drop some code that wasn't trusting snprintf to set errno\nwhen it returns -1.  That would be not-per-spec, and again there's\nno real reason to believe it is a live issue, especially not for\nsnprintfs that pass all of configure's feature checks.\n\nDiscussion: https://postgr.es/m/17245.1534289329@sss.pgh.pa.us","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/e1d19c902e59ad739cb4b6267ee2073a61e86cd3"},{"sha":"a082aed0723c737ec65222730ccede5db5251b4d","author":{"name":"Tomas Vondra","email":"07d6043e15c7eaaf8513ba9a264e5412dbd73bf7@postgresql.org"},"message":"Remove remaining GEODEBUG references from geo_ops.c\n\nCommit a7dc63d904a6044d299aebdf59ad3199b6a9e99d removed most of the\nGEODEBUG occurrences, but there were a couple remaining. So remove\nthem too, to get rid of the macro entirely.\n\nAuthor: Emre Hasegeli\n\nDiscussion: https://www.postgresql.org/message-id/CAE2gYzxF7-5djV6-cEvqQu-fNsnt%3DEqbOURx7ZDg%2BVv6ZMTWbg%40mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/a082aed0723c737ec65222730ccede5db5251b4d"},{"sha":"c4c34008854654279ec30067d72fc5d174d2f42f","author":{"name":"Tomas Vondra","email":"07d6043e15c7eaaf8513ba9a264e5412dbd73bf7@postgresql.org"},"message":"Use the built-in float datatypes to implement geometric types\n\nThis patch makes the geometric operators and functions use the exported\nfunction of the float4/float8 datatypes.  The main reason of doing so is\nto check for underflow and overflow, and to handle NaNs consciously.\n\nThe float datatypes consider NaNs values to be equal and greater than\nall non-NaN values.  This change considers NaNs equal only for equality\noperators.  The placement operators, contains, overlaps, left/right of\netc. continue to return false when NaNs are involved.  We don't need\nto worry about them being considered greater than any-NaN because there\naren't any basic comparison operators like less/greater than for the\ngeometric datatypes.\n\nThe changes may be summarised as:\n\n* Check for underflow, overflow and division by zero\n* Consider NaN values to be equal\n* Return NULL when the distance is NaN for all closest point operators\n* Favour not-NaN over NaN where it makes sense\n\nThe patch also replaces all occurrences of \"double\" as \"float8\".  They\nare the same, but were used inconsistently in the same file.\n\nAuthor: Emre Hasegeli\nReviewed-by: Kyotaro Horiguchi, Tomas Vondra\n\nDiscussion: https://www.postgresql.org/message-id/CAE2gYzxF7-5djV6-cEvqQu-fNsnt%3DEqbOURx7ZDg%2BVv6ZMTWbg%40mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/c4c34008854654279ec30067d72fc5d174d2f42f"},{"sha":"9d0aa4f4d22a4feddbf7c05308fe32b32d14c13f","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"Remove unused configure test for ldopen()\n\nunused since f2cc453dd7e87e800a62a173dea0353bf106668d","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/9d0aa4f4d22a4feddbf7c05308fe32b32d14c13f"},{"sha":"96e98fa2606b2b12805db99196f468152312af14","author":{"name":"Thomas Munro","email":"1ff054ef0838bf068a4b7c40eef026e560a37025@postgresql.org"},"message":"Proof-reading for documentation.\n\nSomebody accidentally a word.  Back-patch to 9.6.\n\nReported-by: Justin Pryzby\nDiscussion: https://postgr.es/m/20180816195431.GA23707%40telsasoft.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/96e98fa2606b2b12805db99196f468152312af14"},{"sha":"ee80124811908ef1d4679296c46e36bd8a32b9de","author":{"name":"Michael Paquier","email":"17b9e1c64588c7fa6419b4d29dc1f4426279ba01@paquier.xyz"},"message":"Mention ownership requirements for REFRESH MATERIALIZED VIEW in docs\n\nAuthor: Dian Fay\nDiscussion: https://postgr.es/m/745abbd2-a1a0-ead8-2cb2-768c16747d97@gmail.com\nBackpatch-through: 9.3","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/ee80124811908ef1d4679296c46e36bd8a32b9de"},{"sha":"00f03118962f32c111e719bd382f3716a353e694","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 19/1621] ALTER TABLE - check for column existence before starting operations\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/1621\nPatch(es): https://www.postgresql.org/message-id/1897070.0DItnajBuJ@pierred-pdoc\nAuthor(s): Pierre Ducroquet","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/00f03118962f32c111e719bd382f3716a353e694"}]}
{"actor":{"display_login":"postgresql-cfbot"}}