{"push_id":1559788290,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"01e0cbc4f687325b825e7953f99f0b16a2bd4e96","before":"5262f7a4fc44f651241d2ff1fa688dd664a34874","commits":[{"sha":"01e0cbc4f687325b825e7953f99f0b16a2bd4e96","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Fix YA unwanted behavioral difference with operator_precedence_warning.\n\nJeff Janes noted that the error cursor position shown for some errors\nwould vary when operator_precedence_warning is turned on.  We'd prefer\nthat option to have no undocumented effects, so this isn't desirable.\nTo fix, make sure that an AEXPR_PAREN node has the same exprLocation\nas its child node.\n\n(Note: it would be a little cheaper to use @2 here instead of an\nexprLocation call, but there are cases where that wouldn't produce\nthe identical answer, so don't do it like that.)\n\nBack-patch to 9.5 where this feature was introduced.\n\nDiscussion: https://postgr.es/m/CAMkU=1ykK+VhhcQ4Ky8KBo9FoaUJH3f3rDQB8TkTXi-ZsBRUkQ@mail.gmail.com","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/01e0cbc4f687325b825e7953f99f0b16a2bd4e96"}]}
{"actor":{"display_login":"postgres-mirror"}}