{"push_id":2650329903,"size":2,"distinct_size":2,"ref":"refs/heads/REL9_5_STABLE","head":"8b444a3539758ce6666679608f3765608f92e0df","before":"2dbcf515ae1e8845d4903169ff81c91806c34d32","commits":[{"sha":"f3be5d3e7891ef6886489cb0c9962d52c5983c70","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Use snprintf not sprintf in pg_waldump's timestamptz_to_str.\n\nThis could only cause an issue if strftime returned a ridiculously\nlong timezone name, which seems unlikely; and it wouldn't qualify\nas a security problem even then, since pg_waldump (nee pg_xlogdump)\nis a debug tool not part of the server.  But gcc 8 has started issuing\nwarnings about it, so let's use snprintf and be safe.\n\nBackpatch to 9.3 where this code was added.\n\nDiscussion: https://postgr.es/m/21789.1529170195@sss.pgh.pa.us","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/f3be5d3e7891ef6886489cb0c9962d52c5983c70"},{"sha":"8b444a3539758ce6666679608f3765608f92e0df","author":{"name":"Tom Lane","email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us"},"message":"Avoid unnecessary use of strncpy in a couple of places in ecpg.\n\nUse of strncpy with a length limit based on the source, rather than\nthe destination, is non-idiomatic and draws warnings from gcc 8.\nReplace with memcpy, which does exactly the same thing in these cases,\nbut with less chance for confusion.\n\nBackpatch to all supported branches.\n\nDiscussion: https://postgr.es/m/21789.1529170195@sss.pgh.pa.us","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/8b444a3539758ce6666679608f3765608f92e0df"}]}
{"actor":{"display_login":"postgres-mirror"}}