{"push_id":2745159108,"size":6,"distinct_size":1,"ref":"refs/heads/commitfest/18/1666","head":"0e27e581fedad0c1b05f171d8f454168f5221145","before":"c454a286f19232d2ce23a9b0811b86cb5832b2ef","commits":[{"sha":"fb421231daaa5228542ef6644cdee505fbc31dba","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"psql: Add option for procedures to \\df","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/fb421231daaa5228542ef6644cdee505fbc31dba"},{"sha":"b2bb3dc0e0d9825640654b9ae0b82c1a747d42ea","author":{"name":"Andres Freund","email":"883768b6dd2c42aea0031b24be8a2da40fef4b64@anarazel.de"},"message":"Defend against some potential spurious compiler warnings in 86eaf208e.\n\nAuthor: David Rowley\nDiscussion: https://postgr.es/m/CAKJS1f-AbCFeFU92GZZYqNOVRnPtUwczSYmR2NHCyf9uHUnNiw@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/b2bb3dc0e0d9825640654b9ae0b82c1a747d42ea"},{"sha":"487bcc6ea6757a563fff188a9551e011d85b6caa","author":{"name":"Andres Freund","email":"883768b6dd2c42aea0031b24be8a2da40fef4b64@anarazel.de"},"message":"doc: Fix reference to \"decoder\" to instead be the correct \"output plugin\".\n\nAuthor: Jonathan Katz\nDiscussion: https://postgr.es/m/DD02DD86-5989-4BFD-8712-468541F68383@postgresql.org\nBackpatch: 9.4-, where logical decoding was added","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/487bcc6ea6757a563fff188a9551e011d85b6caa"},{"sha":"2d3067595299d2ac1f29bbc26a83a99d59b33d4e","author":{"name":"Thomas Munro","email":"1ff054ef0838bf068a4b7c40eef026e560a37025@postgresql.org"},"message":"Pad semaphores to avoid false sharing.\n\nIn a USE_UNNAMED_SEMAPHORES build, the default on Linux and FreeBSD\nsince commit ecb0d20a, we have an array of sem_t objects.  This\nturned out to reduce performance compared to the previous default\nUSE_SYSV_SEMAPHORES on an 8 socket system.  Testing showed that the\nlost performance could be regained by padding the array elements so\nthat they have their own cache lines.  This matches what we do for\nsimilar hot arrays (see LWLockPadded, WALInsertLockPadded).\n\nBack-patch to 10, where unnamed semaphores were adopted as the default\nsemaphore interface on those operating systems.\n\nAuthor: Thomas Munro\nReviewed-by: Andres Freund\nReported-by: Mithun Cy\nTested-by: Mithun Cy, Tom Lane, Thomas Munro\nDiscussion: https://postgr.es/m/CAD__OugYDM3O%2BdyZnnZSbJprSfsGFJcQ1R%3De59T3hcLmDug4_w%40mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/2d3067595299d2ac1f29bbc26a83a99d59b33d4e"},{"sha":"167075be3ab1547e186096bb8e6e448cd8eea5af","author":{"name":"Tomas Vondra","email":"07d6043e15c7eaaf8513ba9a264e5412dbd73bf7@postgresql.org"},"message":"Add strict_multi_assignment and too_many_rows plpgsql checks\n\nUntil now shadowed_variables was the only plpgsql check supported by\nplpgsql.extra_warnings and plpgsql.extra_errors.  This patch introduces\ntwo new checks - strict_multi_assignment and too_many_rows.  Unlike\nshadowed_variables, these new checks are enforced at run-time.\n\nstrict_multi_assignment checks that commands allowing multi-assignment\n(for example SELECT INTO) have the same number of sources and targets.\ntoo_many_rows checks that queries with an INTO clause return one row\nexactly.\n\nThese checks are aimed at cases that are technically valid and allowed,\nbut are often a sign of a bug.  Therefore those checks are expected to\nbe enabled primarily in development and testing environments.\n\nAuthor: Pavel Stehule\nReviewed-by: Stephen Frost, Tomas Vondra\nDiscussion: https://www.postgresql.org/message-id/flat/CAFj8pRA2kKRDKpUNwLY0GeG1OqOp+tLS2yQA1V41gzuSz-hCng@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/167075be3ab1547e186096bb8e6e448cd8eea5af"},{"sha":"0e27e581fedad0c1b05f171d8f454168f5221145","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 18/1666] Moving relation extension locks out of heavyweight lock manager\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/18/1666\nPatch(es): https://www.postgresql.org/message-id/CAD21AoBn8WbOt21MFfj1mQmL2ZD8KVgMHYrOe1F5ozsQC4Z_hw@mail.gmail.com\nAuthor(s): Masahiko Sawada","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/0e27e581fedad0c1b05f171d8f454168f5221145"}]}
{"actor":{"display_login":"postgresql-cfbot"}}