{"push_id":2855814927,"size":1,"distinct_size":1,"ref":"refs/heads/REL_11_STABLE","head":"23aad181f44741c2061ce5caceb307774ac14fb8","before":"834bce0a5293424d127ab72440b9eacc8841051f","commits":[{"sha":"23aad181f44741c2061ce5caceb307774ac14fb8","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Make contrib/unaccent's unaccent() function work when not in search path.\n\nSince the fixes for CVE-2018-1058, we've advised people to schema-qualify\nfunction references in order to fix failures in code that executes under\na minimal search_path setting.  However, that's insufficient to make the\nsingle-argument form of unaccent() work, because it looks up the \"unaccent\"\ntext search dictionary using the search path.\n\nThe most expedient answer seems to be to remove the search_path dependency\nby making it look in the same schema that the unaccent() function itself\nis declared in.  This will definitely work for the normal usage of this\nfunction with the unaccent dictionary provided by the extension.\nIt's barely possible that there are people who were relying on the\nsearch-path-dependent behavior to select other dictionaries with the same\nname; but if there are any such people at all, they can still get that\nbehavior by writing unaccent('unaccent', ...), or possibly\nunaccent('unaccent'::text::regdictionary, ...) if the lookup has to be\npostponed to runtime.\n\nPer complaint from Gunnlaugur Thor Briem.  Back-patch to all supported\nbranches.\n\nDiscussion: https://postgr.es/m/CAPs+M8LCex6d=DeneofdsoJVijaG59m9V0ggbb3pOH7hZO4+cQ@mail.gmail.com","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/23aad181f44741c2061ce5caceb307774ac14fb8"}]}
{"actor":{"display_login":"postgres-mirror"}}