{"push_id":2433670242,"size":8,"distinct_size":1,"ref":"refs/heads/commitfest/18/1533","head":"248ab0926ff50dfbdd7751dcc5ca0bedf962a363","before":"ac3d9edaa1da7466cc2056ebd268c27b5203b3bc","commits":[{"sha":"2b27273435392d1606f0ffc95d73a439a457f08e","author":{"name":"Andrew Dunstan","email":"6b7c097d961f68685fc978cf91eeae17be6cbb45@dunslane.net"},"message":"Optimize btree insertions for common case of increasing values\n\nRemember the last page of an index insert if it's the rightmost leaf\npage. If the next entry belongs on and can fit in the remembered page,\ninsert the new entry there as long as we can get a lock on the page.\nOtherwise, fall back on the more expensive method of searching for\nthe right place to insert the entry.\n\nThis provides a performance improvement for the common case where an\nindex entry is for monotonically increasing or nearly monotonically\nincreasing value such as an identity field or a current timestamp.\n\nPavan Deolasee\nReviewed by Claudio Freire, Simon Riggs and Peter Geoghegan\n\nDiscussion: https://postgr.es/m/CABOikdM9DrupjyKZZFM5k8-0RCDs1wk6JzEkg7UgSW6QzOwMZw@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/2b27273435392d1606f0ffc95d73a439a457f08e"},{"sha":"1d494b622fa9dfdbd7213f357cd38def0125a322","author":{"name":"Andrew Dunstan","email":"6b7c097d961f68685fc978cf91eeae17be6cbb45@dunslane.net"},"message":"Remove two tests inadvertently added in 2b27273435","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/1d494b622fa9dfdbd7213f357cd38def0125a322"},{"sha":"1b89c2188bd38eac68251f16051859996128f2d0","author":{"name":"Alvaro Herrera","email":"7cf34a26c111482b1b00703daedc3ff840f1e2cf@alvh.no-ip.org"},"message":"Fix typo","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/1b89c2188bd38eac68251f16051859996128f2d0"},{"sha":"555ee77a9668e3f1b03307055b5027e13bf1a715","author":{"name":"Alvaro Herrera","email":"7cf34a26c111482b1b00703daedc3ff840f1e2cf@alvh.no-ip.org"},"message":"Handle INSERT .. ON CONFLICT with partitioned tables\n\nCommit eb7ed3f30634 enabled unique constraints on partitioned tables,\nbut one thing that was not working properly is INSERT/ON CONFLICT.\nThis commit introduces a new node keeps state related to the ON CONFLICT\nclause per partition, and fills it when that partition is about to be\nused for tuple routing.\n\nAuthor: Amit Langote, Álvaro Herrera\nReviewed-by: Etsuro Fujita, Pavan Deolasee\nDiscussion: https://postgr.es/m/20180228004602.cwdyralmg5ejdqkq@alvherre.pgsql","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/555ee77a9668e3f1b03307055b5027e13bf1a715"},{"sha":"186b6df2e62251e5e1f3cae8a3257c7226f4188c","author":{"name":"Alvaro Herrera","email":"7cf34a26c111482b1b00703daedc3ff840f1e2cf@alvh.no-ip.org"},"message":"Fix test impredictability\n\nTest 'triggers' fails when another one creates triggers concurrently at\nsome precise time, because of a missing WHERE clause.\n\nPer buildfarm members snapper, desmoxytes.","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/186b6df2e62251e5e1f3cae8a3257c7226f4188c"},{"sha":"530bcf7581574d5b0f26c2eaeef1c32bbcd37907","author":{"name":"Alvaro Herrera","email":"7cf34a26c111482b1b00703daedc3ff840f1e2cf@alvh.no-ip.org"},"message":"Fix thinko in comment\n\nThe listed numbers disagreed with the ones being used in the symbols;\nbut instead of just fixing the numbers in the comment, use the symbolic\nname instead, which seems clearer.\n\nThis has been wrong all along, so apply back to 9.5 where BRIN was\nintroduced.\n\nReported-by: Tomas Vondra\nDiscussion: https://postgr.es/m/5ff514f2-8b1e-6366-b11c-8e2ed442562d@2ndquadrant.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/530bcf7581574d5b0f26c2eaeef1c32bbcd37907"},{"sha":"64f85894ad2730fb1449a8e81dd8026604e9a546","author":{"name":"Teodor Sigaev","email":"3a52d66b4cc78e45607bfd6c1ee78628c0e18f47@sigaev.ru"},"message":"Set random seed for pgbench.\n\nSetting random could increase reproducibility of test in some cases. Patch\nsuggests three providers for seed: time (default), strong random\ngenerator (if available) and unsigned constant. Seed could be set from\ncommand line or enviroment variable.\n\nAuthor: Fabien Coelho\nReviewed by: Chapman Flack\nDiscussion: https://www.postgresql.org/message-id/flat/20160407082711.q7iq3ykffqxcszkv@alap3.anarazel.de","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/64f85894ad2730fb1449a8e81dd8026604e9a546"},{"sha":"248ab0926ff50dfbdd7751dcc5ca0bedf962a363","author":{"name":"Commitfest Bot","email":"aab6a594935fe5db0d690bc154b19f642bfbe9d7@cputube.org"},"message":"[CF 18/1533] Add support for ON UPDATE/DELETE actions on ALTER CONSTRAINT\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/18/1533\nPatch(es): https://www.postgresql.org/message-id/CAJghg4K_U%3DKJg6K156kWm2YmOXZmeCzUzitmP4RH%3DBM4Xu%2BcWQ%40mail.gmail.com\nAuthor(s): Matheus Oliveira","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/248ab0926ff50dfbdd7751dcc5ca0bedf962a363"}]}
{"actor":{"display_login":"postgresql-cfbot"}}