{"push_id":2373025212,"size":10,"distinct_size":1,"ref":"refs/heads/commitfest/17/1426","head":"6fc48ef474d2473b06b9036565e6072bb37ec635","before":"4b4b5960e9c2e868b3c85a624f394f16947c504c","commits":[{"sha":"7240962f8626ff09bb8f9e71ecdb074775bdd035","author":{"name":"Magnus Hagander","email":"96ad6b06de7111eee5a9c968ba6978bf7a7a179d@hagander.net"},"message":"Fix msvc builds for ActivePerl > 5.24\n\nFrom this version ActivePerl ships both a .lib and a .a file for the\nperl library, which our code would detect as there being no library\navailable. Instead, we should pick the .lib version and use that.\n\nReport and suggested fix in bug #15065\n\nAuthor: Heath Lord","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/7240962f8626ff09bb8f9e71ecdb074775bdd035"},{"sha":"81b9b5ce490a645bde8df203ec4a3b2903d88f31","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Make gistvacuumcleanup() count the actual number of index tuples.\n\nPreviously, it just returned the heap tuple count, which might be only an\nestimate, and would be completely the wrong thing if the index is partial.\nSince this function scans every index page anyway to find free pages,\nit's practically free to count the surviving index tuples.  Let's do that\nand return an accurate count.\n\nThis is easily visible as a wrong reltuples value for a partial GiST\nindex following VACUUM, so back-patch to all supported branches.\n\nAndrey Borodin, reviewed by Michail Nikolaev\n\nDiscussion: https://postgr.es/m/151956654251.6915.675951950408204404.pgcf@coridan.postgresql.org","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/81b9b5ce490a645bde8df203ec4a3b2903d88f31"},{"sha":"2b8c94e1b4a86907fceef87840c32d3703f7e161","author":{"name":"Fujii Masao","email":"c29e6ecdbc28d8481e10f45ba12ee78dec82f1ee@postgresql.org"},"message":"Improve tab-completion for ALTER INDEX RESET/SET.\n\nAuthor: Masahiko Sawada\nDiscussion: https://postgr.es/m/CAD21AoDSGfB0G4egOy2UvBT=uihojuh-syxgSipj+XNkpWdVzQ@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/2b8c94e1b4a86907fceef87840c32d3703f7e161"},{"sha":"34db06ef9a1d7f36391c64293bf1e0ce44a33915","author":{"name":"Robert Haas","email":"93159bdbbeed5b47be970d58edfbdf1c3ce55e4c@postgresql.org"},"message":"shm_mq: Reduce spinlock usage.\n\nPreviously, mq_bytes_read and mq_bytes_written were protected by the\nspinlock, but that turns out to cause pretty serious spinlock\ncontention on queries which send many tuples through a Gather or\nGather Merge node.  This patches changes things so that we instead\nread and write those values using 8-byte atomics.  Since mq_bytes_read\ncan only be changed by the receiver and mq_bytes_written can only be\nchanged by the sender, the only purpose of the spinlock is to prevent\nreads and writes of these values from being torn on platforms where\n8-byte memory access is not atomic, making the conversion fairly\nstraightforward.\n\nTesting shows that this produces some slowdown if we're using emulated\n64-bit atomics, but since they should be available on any platform\nwhere performance is a primary concern, that seems OK.  It's faster,\nsometimes a lot faster, on platforms where such atomics are available.\n\nPatch by me, reviewed by Andres Freund, who also suggested the\ndesign.  Also tested by Rafia Sabih.\n\nDiscussion: http://postgr.es/m/CA+TgmoYuK0XXxmUNTFT9TSNiBtWnRwasBcHHRCOK9iYmDLQVPg@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/34db06ef9a1d7f36391c64293bf1e0ce44a33915"},{"sha":"497171d3e2aaeea3b30d710b4e368645ad07ae43","author":{"name":"Robert Haas","email":"93159bdbbeed5b47be970d58edfbdf1c3ce55e4c@postgresql.org"},"message":"shm_mq: Have the receiver set the sender's less frequently.\n\nInstead of marking data from the ringer buffer consumed and setting the\nsender's latch for every message, do it only when the amount of data we\ncan consume is at least 1/4 of the size of the ring buffer, or when no\ndata remains in the ring buffer.  This is dramatically faster in my\ntesting; apparently, the savings from sending signals less frequently\noutweighs the benefit of letting the sender know about available buffer\nspace sooner.\n\nPatch by me, reviewed by Andres Freund and tested by Rafia Sabih.\n\nDiscussion: http://postgr.es/m/CA+TgmoYK7RFj6r7KLEfSGtYZCi3zqTRhAz8mcsDbUAjEmLOZ3Q@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/497171d3e2aaeea3b30d710b4e368645ad07ae43"},{"sha":"1733460f0205fc6d6bbe4c14911049a918c6e073","author":{"name":"Robert Haas","email":"93159bdbbeed5b47be970d58edfbdf1c3ce55e4c@postgresql.org"},"message":"postgres_fdw: Fourth attempt to stabilize regression tests.\n\nCommit 1bc0100d270e5bcc980a0629b8726a32a497e788 added this test, and\ncommits 882ea509fe7a4711fe25463427a33262b873dfa1,\n958e20e42d6c346ab89f6c72e4262230161d1663,\n4fa396464e5fe238b7994535182f28318c61c78e tried to stabilize it.  It's\nstill not stable, so keep trying.\n\nThe latest comment from Tom Lane is that disabling autovacuum seems\nlike a good strategy, but we might need to do it on more tables, hence\nthis patch.\n\nEtsuro Fujita\n\nDiscussion: http://postgr.es/m/5A9928F1.2010206@lab.ntt.co.jp","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/1733460f0205fc6d6bbe4c14911049a918c6e073"},{"sha":"fd1a421fe66173fb9b85d3fe150afde8e812cbe4","author":{"name":"Peter Eisentraut","email":"2f47089682e4afbd5de3eea4edffc95dfc1eb9de@gmx.net"},"message":"Add prokind column, replacing proisagg and proiswindow\n\nThe new column distinguishes normal functions, procedures, aggregates,\nand window functions.  This replaces the existing columns proisagg and\nproiswindow, and replaces the convention that procedures are indicated\nby prorettype == 0.  Also change prorettype to be VOIDOID for procedures.\n\nReviewed-by: Tom Lane <tgl@sss.pgh.pa.us>\nReviewed-by: Michael Paquier <michael@paquier.xyz>","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/fd1a421fe66173fb9b85d3fe150afde8e812cbe4"},{"sha":"e94f2bc809a0c684185666f19d81f6496e732a3a","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Fix pgbench TAP test to work in VPATH builds.\n\nPreviously, it'd try to create log files under the source directory\nnot the build directory.  This fell over if the source isn't writable\nby the building user.\n\nFabien Coelho\n\nDiscussion: https://postgr.es/m/alpine.DEB.2.20.1801101038340.2283@lancre","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/e94f2bc809a0c684185666f19d81f6496e732a3a"},{"sha":"0b1d1a038babff4aadf0862c28e7b667f1b12a30","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Fix VM buffer pin management in heap_lock_updated_tuple_rec().\n\nSloppy coding in this function could lead to leaking a VM buffer pin,\nor to attempting to free the same pin twice.  Repair.  While at it,\nreduce the code's tendency to free and reacquire the same page pin.\n\nBack-patch to 9.6; before that, this routine did not concern itself\nwith VM pages.\n\nAmit Kapila and Tom Lane\n\nDiscussion: https://postgr.es/m/CAA4eK1KJKwhc=isgTQHjM76CAdVswzNeAuZkh_cx-6QgGkSEgA@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/0b1d1a038babff4aadf0862c28e7b667f1b12a30"},{"sha":"6fc48ef474d2473b06b9036565e6072bb37ec635","author":{"name":"Commitfest Bot","email":"aab6a594935fe5db0d690bc154b19f642bfbe9d7@cputube.org"},"message":"[CF 17/1426] Test partition-wise join with partitioned tables containing default partition\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/17/1426\nPatch(es): https://www.postgresql.org/message-id/CAKcux6nF%3DwZzztNY%3DhOcsF5XPvNCB5ryb9A9YvVfycQj47Tk4Q%40mail.gmail.com\nAuthor(s): rajkumar raghuwanshi","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/6fc48ef474d2473b06b9036565e6072bb37ec635"}]}
{"actor":{"display_login":"postgresql-cfbot"}}