{"push_id":1160358965,"size":1,"distinct_size":1,"ref":"refs/heads/json","head":"9c97b5828632d114aefc0d827fa6645cbba66f38","before":"0e192f386572c7daff51d68941f7484f92363852","commits":[{"sha":"9c97b5828632d114aefc0d827fa6645cbba66f38","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Revisit error message details for JSON input parsing.\n\nInstead of identifying error locations only by line number (which could\nbe entirely unhelpful with long input lines), provide a fragment of the\ninput text too, placing this info in a new CONTEXT entry.  Make the\nerror detail messages conform more closely to style guidelines, fix\nfailure to expose some of them for translation, ensure compiler can\ncheck formats against supplied parameters.\n\n(cherry-picked from 80edfd76591fdb9beec061de3c05ef4e9d96ce56)\n\nAuthor:             Álvaro Hernández Tortosa <aht@8kdata.com>\nDate:               Tue Jun 14 22:14:05 UTC 2016","distinct":true,"url":"https://api.github.com/repos/ahachete/gpdb/commits/9c97b5828632d114aefc0d827fa6645cbba66f38"}]}
{"actor":{"display_login":"ahachete"}}