{"push_id":2446970184,"size":7,"distinct_size":1,"ref":"refs/heads/commitfest/17/1494","head":"c8d2883861a4fbae1d0332c990a18cf54358c40a","before":"5749052123b54ee169d7af53ccf427c7795dfb9c","commits":[{"sha":"e5eb4fa87331821423b362be5ea4b18e873d5b27","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Remove obsolete SLRU wrapping and warnings from predicate.c.\n\nWhen SSI was developed, slru.c was limited to segment files with names in\nthe range 0000-FFFF.  This didn't allow enough space for predicate.c to\nstore every possible XID when spilling old transactions to disk, so it\nwould wrap around sooner and print warnings.  Since commits 638cf09e and\n73c986ad increased the number of segment files slru.c could manage, that\nbehavior is unnecessary.  Therefore remove that code.\n\nAlso remove the macro OldSerXidSegment, which has been unused since\n4cd3fb6e.\n\nThomas Munro, reviewed by Anastasia Lubennikova\n\nDiscussion: https://postgr.es/m/CAEepm=3XfsTSxgEbEOmxu0QDiXy0o18NUg2nC89JZcCGE+XFPA@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/e5eb4fa87331821423b362be5ea4b18e873d5b27"},{"sha":"4a33bb59dfc33566f04e18ab5e1f90b8e7461052","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Ensure that WAL pages skipped by a forced WAL switch are zero-filled.\n\nIn the previous coding, skipped pages were mostly zeroes, but they still\nhad valid WAL page headers.  That makes them very much less compressible\nthan an unbroken string of zeroes would be --- about 10X worse for bzip2\ncompression, for instance.  We don't need those headers, so tweak the logic\nso that we zero them out.\n\nChapman Flack, reviewed by Daniel Gustafsson\n\nDiscussion: https://postgr.es/m/579297F8.7020107@anastigmatix.net","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/4a33bb59dfc33566f04e18ab5e1f90b8e7461052"},{"sha":"11002f8afa551f4673aa6a7b62c1872c233e6052","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Fix bogus provolatile/proparallel markings on a few built-in functions.\n\nRichard Yen reported that pg_upgrade failed if the target cluster had\nforce_parallel_mode = on, because binary_upgrade_create_empty_extension()\nis marked parallel restricted, allowing it to be executed in parallel\nmode, which complains because it tries to acquire an XID.\n\nIn general, no function that might try to modify database data should\nbe considered parallel safe or restricted, since execution of it might\nforce XID acquisition.  We found several other examples of this mistake.\n\nFurthermore, functions that execute user-supplied SQL queries or query\nfragments, or pull data from user-supplied cursors, had better be marked\nboth volatile and parallel unsafe, because we don't know what the supplied\nquery or cursor might try to do.  There were several tsquery and XML\nfunctions that had the wrong proparallel marking for this, and some of\nthem were even mislabeled as to volatility.\n\nAll these bugs are old, dating back to 9.6 for the proparallel mistakes\nand much further for the provolatile mistakes.  We can't force a\ncatversion bump in the back branches, but we can at least ensure that\ninstallations initdb'd in future have the right values.\n\nThomas Munro and Tom Lane\n\nDiscussion: https://postgr.es/m/CAEepm=2sNDScSLTfyMYu32Q=ob98ZGW-vM_2oLxinzSABGQ6VA@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/11002f8afa551f4673aa6a7b62c1872c233e6052"},{"sha":"9a895462d940c0694042059f90e5f63a0a517ded","author":{"name":"Fujii Masao","email":"c29e6ecdbc28d8481e10f45ba12ee78dec82f1ee@postgresql.org"},"message":"Enhance pg_stat_wal_receiver view to display host and port of sender server.\n\nPreviously there was no way in the standby side to find out the host and port\nof the sender server that the walreceiver was currently connected to when\nmultiple hosts and ports were specified in primary_conninfo. For that purpose,\nthis patch adds sender_host and sender_port columns into pg_stat_wal_receiver\nview. They report the host and port that the active replication connection\ncurrently uses.\n\nBump catalog version.\n\nAuthor: Haribabu Kommi\nReviewed-by: Michael Paquier and me\n\nDiscussion: https://postgr.es/m/CAJrrPGcV_aq8=cdqkFhVDJKEnDQ70yRTTdY9RODzMnXNrCz2Ow@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/9a895462d940c0694042059f90e5f63a0a517ded"},{"sha":"d87510a524f36a630cfb34cc392e95e959a1b0dc","author":{"name":"Andres Freund","email":"c6cbfe878b4ee67646e7630734db67f536518d54@anarazel.de"},"message":"Combine options for RangeVarGetRelidExtended() into a flags argument.\n\nA followup patch will add a SKIP_LOCKED option. To avoid introducing\nevermore arguments, breaking existing callers each time, introduce a\nflags argument. This'll no doubt break a few external users...\n\nAlso change the MISSING_OK behaviour so a DEBUG1 debug message is\nemitted when a relation is not found.\n\nAuthor: Nathan Bossart\nReviewed-By: Michael Paquier and Andres Freund\nDiscussion: https://postgr.es/m/20180306005349.b65whmvj7z6hbe2y@alap3.anarazel.de","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/d87510a524f36a630cfb34cc392e95e959a1b0dc"},{"sha":"3e256e550672657375fc3058b2b8ff6568d65cef","author":{"name":"Andres Freund","email":"c6cbfe878b4ee67646e7630734db67f536518d54@anarazel.de"},"message":"Add SKIP_LOCKED option to RangeVarGetRelidExtended().\n\nThis will be used for VACUUM (SKIP LOCKED).\n\nAuthor: Nathan Bossart\nReviewed-By: Michael Paquier and Andres Freund\nDiscussion: https://postgr.es/m/20180306005349.b65whmvj7z6hbe2y@alap3.anarazel.de","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/3e256e550672657375fc3058b2b8ff6568d65cef"},{"sha":"c8d2883861a4fbae1d0332c990a18cf54358c40a","author":{"name":"Commitfest Bot","email":"aab6a594935fe5db0d690bc154b19f642bfbe9d7@cputube.org"},"message":"[CF 17/1494] Support optional message in backend cancellation/termination\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/1494\nPatch(es): https://www.postgresql.org/message-id/9D842953-1B69-43D6-8C06-7797E2F1095A%40yesql.se\nAuthor(s): Daniel Gustafsson","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/c8d2883861a4fbae1d0332c990a18cf54358c40a"}]}
{"actor":{"display_login":"postgresql-cfbot"}}