{"push_id":2112953048,"size":6,"distinct_size":1,"ref":"refs/heads/commitfest/15/772","head":"d423516782cf69b29a08fef2131e5969d49c6091","before":"498086adfc78b3e2e8c0c8e7ed613b0e2b325925","commits":[{"sha":"20d9adab60754ac71b0b500c91c45e12e940b3ce","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Revert \"Allow --with-bonjour to work with non-macOS implementations of Bonjour.\"\n\nUpon further review, our Bonjour code doesn't actually work with the\nAvahi not-too-compatible compatibility library.  While you can get it\nto work on non-macOS platforms if you link to Apple's own mDNSResponder\ncode, there don't seem to be many people who care about that.  Leaving in\nthe AC_SEARCH_LIBS call seems more likely to encourage people to build\nbroken configurations than to do anything very useful.\n\nHence, remove the AC_SEARCH_LIBS call and put in a warning comment instead.\n\nDiscussion: https://postgr.es/m/2D8331C5-D64F-44C1-8717-63EDC6EAF7EB@brightforge.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/20d9adab60754ac71b0b500c91c45e12e940b3ce"},{"sha":"9be95ef156e7c2ae0924300acddd483504fa33b3","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Fix bogus logic for checking executables' versions within pg_upgrade.\n\nSomebody messed up a refactoring here.  As it stood, we'd check pg_ctl's\n--version output twice for each cluster.  Worse, the first check for the\nnew cluster's version happened before we'd done any validate_exec checks\nthere, breaking the check ordering the code intended.\n\nA. Akenteva\n\nDiscussion: https://postgr.es/m/f9266a85d918a3cf3a386b5148aee666@postgrespro.ru","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/9be95ef156e7c2ae0924300acddd483504fa33b3"},{"sha":"6c3a7ba5bb0f960ed412b1c36e815f53347b3d79","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Fix typo in ALTER SYSTEM output.\n\nThe header comment written into postgresql.auto.conf by ALTER SYSTEM\nshould match what initdb put there originally.\n\nFeike Steenbergen\n\nDiscussion: https://postgr.es/m/CAK_s-G0KcKdO=0hqZkwb3s+tqZuuHwWqmF5BDsmoO9FtX75r0g@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/6c3a7ba5bb0f960ed412b1c36e815f53347b3d79"},{"sha":"5ecc0d738e5864848bbc2d1d97e56d5846624ba2","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Restrict lo_import()/lo_export() via SQL permissions not hard-wired checks.\n\nWhile it's generally unwise to give permissions on these functions to\nanyone but a superuser, we've been moving away from hard-wired permission\nchecks inside functions in favor of using the SQL permission system to\ncontrol access.  Bring lo_import() and lo_export() into compliance with\nthat approach.\n\nIn particular, this removes the manual configuration option\nALLOW_DANGEROUS_LO_FUNCTIONS.  That dates back to 1999 (commit 4cd4a54c8);\nit's unlikely anyone has used it in many years.  Moreover, if you really\nwant such behavior, now you can get it with GRANT ... TO PUBLIC instead.\n\nMichael Paquier\n\nDiscussion: https://postgr.es/m/CAB7nPqRHmNOYbETnc_2EjsuzSM00Z+BWKv9sy6tnvSd5gWT_JA@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/5ecc0d738e5864848bbc2d1d97e56d5846624ba2"},{"sha":"ae20b23a9e7029f31ee902da08a464d968319f56","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Refactor permissions checks for large objects.\n\nUp to now, ACL checks for large objects happened at the level of\nthe SQL-callable functions, which led to CVE-2017-7548 because of a\nmissing check.  Push them down to be enforced in inv_api.c as much\nas possible, in hopes of preventing future bugs.  This does have the\neffect of moving read and write permission errors to happen at lo_open\ntime not loread or lowrite time, but that seems acceptable.\n\nMichael Paquier and Tom Lane\n\nDiscussion: https://postgr.es/m/CAB7nPqRHmNOYbETnc_2EjsuzSM00Z+BWKv9sy6tnvSd5gWT_JA@mail.gmail.com","distinct":false,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/ae20b23a9e7029f31ee902da08a464d968319f56"},{"sha":"d423516782cf69b29a08fef2131e5969d49c6091","author":{"name":"Commitfest Bot","email":"aab6a594935fe5db0d690bc154b19f642bfbe9d7@cputube.org"},"message":"[CF 15/772] Make async slave to wait for lsn to be replayed\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/15/772\nPatch(es): https://www.postgresql.org/message-id/c5c4141530ac1063da2a808c2817921c%40postgrespro.ru\nAuthor(s): Ivan Kartyshov","distinct":true,"url":"https://api.github.com/repos/postgresql-cfbot/postgresql/commits/d423516782cf69b29a08fef2131e5969d49c6091"}]}
{"actor":{"display_login":"postgresql-cfbot"}}