{"push_id":2701408750,"size":7,"distinct_size":1,"ref":"refs/heads/commitfest/18/1706","head":"52c26f548d4cd42b64f7a03f3f89648492251607","before":"4c2d960fb65f323a006f3ac390e26ce60d9cc99b","commits":[{"sha":"4513d3a4be0bb7d0141f8b7eaf669a55c08e41b0","author":{"name":"Jeff Davis","email":"a6043a059331789899fcd6238d9fdd7ab2ab417a@postgresql.org"},"message":"Add test for partitionwise join involving default partition.\n\nAuthor: Rajkumar Raghuwanshi\nReviewed-by: Ashutosh Bapat\nDiscussion: https://postgr.es/m/CAKcux6ky5YeZAY74qSh-ayPZZEQchz092g71iXXbC0%2BE3xoscA%40mail.gmail.com\nDiscussion: https://postgr.es/m/CAKcux6kOQ85Xtzxu3tM1mR7Vk%3D7Z2e4rG7dL1iMZqPgLMpxQYg%40mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/4513d3a4be0bb7d0141f8b7eaf669a55c08e41b0"},{"sha":"8fb68aa2655762beed237ea04e2c6c490cf1ed10","author":{"name":"Andrew Dunstan","email":"02e0a999c50b1f88df7a8f5a04e1b76b35ea6a88@dunslane.net"},"message":"Print DEBUG2 like that rather than as DEBUG\n\nDEBUG is an alias for DEBUG2, but we want DEBUG2 to show in the settings\nno matter how it was spelled.\n\nTakeshi Ideriha\n\nDiscussion: https://postgr.es/m/4E72940DA2BF16479384A86D54D0988A5678EC03@G01JPEXMBKW04","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/8fb68aa2655762beed237ea04e2c6c490cf1ed10"},{"sha":"0ce5cf2ef24f638ff05569d027135fa1c7683a71","author":{"name":"Alvaro Herrera","email":"3c84f0de6f8a0f296d36cdd9f57fa166641c96b1@alvh.no-ip.org"},"message":"Allow replication slots to be dropped in single-user mode\n\nStarting with commit 9915de6c1cb2, replication slot drop uses a\ncondition variable sleep to wait until the current user of the slot goes\naway.  This is more user friendly than the previous behavior of erroring\nout if the slot is in use, but it fails with a not-for-user-consumption\nerror message in single-user mode; plus, if you're using single-user\nmode because you don't want to start the server in the regular mode\n(say, disk is full and WAL won't recycle because of the slot), it's\ninconvenient.\n\nFix by skipping the cond variable sleep in single-user mode, since\nthere can't be anybody to wait for anyway.\n\nReported-by: tushar <tushar.ahuja@enterprisedb.com>\nAuthor: Álvaro Herrera <alvherre@alvh.no-ip.org>\nDiscussion: https://postgr.es/m/3b2f809f-326c-38dd-7a9e-897f957a4eb1@enterprisedb.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/0ce5cf2ef24f638ff05569d027135fa1c7683a71"},{"sha":"e34ec136201df07a05a83825ebff7fffb9043598","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"Allow CALL with polymorphic type arguments\n\nIn order to be able to resolve polymorphic types, we need to set fn_expr\nbefore invoking the procedure.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/e34ec136201df07a05a83825ebff7fffb9043598"},{"sha":"2e78c5b522a91c7893decd92d6f5b31fef0027bd","author":{"name":"Peter Eisentraut","email":"c50e6bf7013fce877ffb25104d778a36de31e297@gmx.net"},"message":"Fix assert in nested SQL procedure call\n\nWhen executing CALL in PL/pgSQL, we need to set a snapshot before\ninvoking the to-be-called procedure.  Otherwise, the to-be-called\nprocedure might end up running without a snapshot.  For LANGUAGE SQL\nprocedures, this would result in an assertion failure.  (For most other\nlanguages, this is usually not a problem, because those use SPI and SPI\nsets snapshots in most cases.)  Setting the snapshot restores the\nbehavior of how CALL worked when it was handled as a generic SQL\nstatement in PL/pgSQL (exec_stmt_execsql()).\n\nThis change revealed another problem:  In SPI_commit(), we popped the\nactive snapshot before committing the transaction, to avoid \"snapshot %p\nstill active\" errors.  However, there is no particular reason why only\nat most one snapshot should be on the stack.  So change this to pop all\nactive snapshots instead of only one.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/2e78c5b522a91c7893decd92d6f5b31fef0027bd"},{"sha":"eb270b00b2d60e751545d4b808642395c901b668","author":{"name":"Michael Paquier","email":"17b9e1c64588c7fa6419b4d29dc1f4426279ba01@paquier.xyz"},"message":"Add note in pg_rewind documentation about read-only files\n\nWhen performing pg_rewind, the presence of a read-only file which is not\naccessible for writes will cause a failure while processing.  This can\ncause the control file of the target data folder to be truncated,\ncausing it to not be reusable with a successive run.\n\nAlso, when pg_rewind fails mid-flight, there is likely no way to be able\nto recover the target data folder anyway, in which case a new base\nbackup is the best option.  A note is added in the documentation as\nwell about.\n\nReported-by: Christian H.\nAuthor: Michael Paquier\nReviewed-by: Andrew Dunstan\nDiscussion: https://postgr.es/m/20180104200633.17004.16377%40wrigleys.postgresql.org","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/eb270b00b2d60e751545d4b808642395c901b668"},{"sha":"52c26f548d4cd42b64f7a03f3f89648492251607","author":{"name":"Commitfest Bot","email":"b9e638e07cc2e2abf56c9c0cad7954f2e3bc1641@cputube.org"},"message":"[CF 18/1706] cost_sort improvement\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/1706\nPatch(es): https://www.postgresql.org/message-id/803ccdce-39ef-f1c3-3c65-c79959f7081d@sigaev.ru\nAuthor(s): Fedor Sigaev","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/52c26f548d4cd42b64f7a03f3f89648492251607"}]}
{"actor":{"display_login":"postgresql-cfbot"}}