{"push_id":3168517130,"size":7,"distinct_size":1,"ref":"refs/heads/commitfest/21/1853","head":"21145538fb0f82336dbdd4b1aa62f9ff7015ff24","before":"e022f52b51ff46da8f8430e9474573d9955b2213","commits":[{"sha":"1e504f01da11db0181d7b28bb30cb5eeb0767184","author":{"name":"Michael Paquier","email":"17b9e1c64588c7fa6419b4d29dc1f4426279ba01@paquier.xyz"},"message":"Ignore inherited temp relations from other sessions when truncating\n\nInheritance trees can include temporary tables if the parent is\npermanent, which makes possible the presence of multiple temporary\nchildren from different sessions.  Trying to issue a TRUNCATE on the\nparent in this scenario causes a failure, so similarly to any other\nqueries just ignore such cases, which makes TRUNCATE work\ntransparently.\n\nThis makes truncation behave similarly to any other DML query working on\nthe parent table with queries which need to be work on the children.  A\nset of isolation tests is added to cover basic cases.\n\nReported-by: Zhou Digoal\nAuthor: Amit Langote, Michael Paquier\nDiscussion: https://postgr.es/m/15565-ce67a48d0244436a@postgresql.org\nBackpatch-through: 9.4","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/1e504f01da11db0181d7b28bb30cb5eeb0767184"},{"sha":"b450abd2551ee30b5bc289c662f5728d87e13a39","author":{"name":"Alexander Korotkov","email":"1c137998207470ad0f56303c4fc305487ec0232f@postgresql.org"},"message":"Remove entry tree root conflict checking from GIN predicate locking\n\nAccording to README we acquire predicate locks on entry tree leafs and posting\ntree roots.  However, when ginFindLeafPage() is going to lock leaf in exclusive\nmode, then it checks root for conflicts regardless whether it's a entry or\nposting tree.  Assuming that we never place predicate lock on entry tree root\n(excluding corner case when root is leaf), this check is redundant.  This\ncommit removes this check.  Now, root conflict checking is controlled by\nseparate argument of ginFindLeafPage().\n\nDiscussion: https://postgr.es/m/CAPpHfdv7rrDyy%3DMgsaK-L9kk0AH7az0B-mdC3w3p0FSb9uoyEg%40mail.gmail.com\nAuthor: Alexander Korotkov\nBackpatch-through: 11","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/b450abd2551ee30b5bc289c662f5728d87e13a39"},{"sha":"5c828307973366f424438b848d4cca6ef98c032e","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"pg_dump: Add missing newline to error message","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/5c828307973366f424438b848d4cca6ef98c032e"},{"sha":"ae4472c619341ff0517254d395d74796277622e6","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"Remove obsolete IndexIs* macros\n\nRemove IndexIsValid(), IndexIsReady(), IndexIsLive() in favor of\naccessing the index structure directly.  These macros haven't been\nused consistently, and the original reason of maintaining source\ncompatibility with PostgreSQL 9.2 is gone.\n\nDiscussion: https://www.postgresql.org/message-id/flat/d419147c-09d4-6196-5d9d-0234b230880a%402ndquadrant.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/ae4472c619341ff0517254d395d74796277622e6"},{"sha":"0c6f4f9212cf3155b258910acf80fec89f49b767","author":{"name":"Alexander Korotkov","email":"1c137998207470ad0f56303c4fc305487ec0232f@postgresql.org"},"message":"Reduce length of GIN predicate locking isolation test suite\n\nIsolation test suite of GIN predicate locking was criticized for being too slow,\nespecially under Valgrind.  This commit is intended to accelerate it.  Tests are\nsimplified in the following ways.\n\n  1) Amount of data is reduced.  We're now close to the minimal amount of data,\n     which produces at least one posting tree and at least two pages of entry\n     tree.\n  2) Three isolation tests are merged into one.\n  3) Only one tuple is queried from posting tree.  So, locking of index is the\n     same, but tuple locks are not propagated to relation lock.  Also, it is\n     faster.\n  4) Test cases itself are simplified.  Now each test case run just one INSERT\n     and one SELECT involving GIN, which either conflict or not.\n\nDiscussion: https://postgr.es/m/20181204000740.ok2q53nvkftwu43a%40alap3.anarazel.de\nReported-by: Andres Freund\nTested-by: Andrew Dunstan\nAuthor: Alexander Korotkov\nBackpatch-through: 11","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/0c6f4f9212cf3155b258910acf80fec89f49b767"},{"sha":"f7ea1a42337f45efed7c4d44f50f62a55e60d30c","author":{"name":"Michael Paquier","email":"17b9e1c64588c7fa6419b4d29dc1f4426279ba01@paquier.xyz"},"message":"Clarify referential actions in docs of CREATE/ALTER TABLE\n\nThe documentation of ON DELETE and ON UPDATE uses the term \"action\",\nwhich is also used on the ALTER TABLE page for other purposes.  This\ncommit renames the term to \"referential_action\", which is more\nconsistent with the SQL specification.  The new term is now used on the\ndocumentation of both CREATE TABLE and ALTER TABLE for consistency.\n\nReported-by: Brigitte Blanc-Lafay\nAuthor: Lætitia Avrot\nReviewed-by: Álvaro Herrera\nDiscussion: https://postgr.es/m/CAB_COdiHEVVs0uB+uYCjjYUwQ4YFFekppq+Xqv6qAM8+cd42gA@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/f7ea1a42337f45efed7c4d44f50f62a55e60d30c"},{"sha":"21145538fb0f82336dbdd4b1aa62f9ff7015ff24","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 21/1853] improve pgbench doc about prepared statements\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/21/1853\nPatch(es): https://www.postgresql.org/message-id/20181203.143315.2134125635511306803.t-ishii@sraoss.co.jp\nAuthor(s): Tatsuo Ishii","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/21145538fb0f82336dbdd4b1aa62f9ff7015ff24"}]}
{"actor":{"display_login":"postgresql-cfbot"}}