{"push_id":1910025969,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"13f03a001e4d841b6a27c0c9c3fe14e1fb2aad80","before":"77d2c00af78ee12ae0d1cea34605f1e7af3f6d93","commits":[{"sha":"9bf4068cc321a4d44ac54089ab651a49d89bb567","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Fix datumSerialize infrastructure to not crash on non-varlena data.\n\nCommit 1efc7e538 did a poor job of emulating existing logic for touching\nDatums that might be expanded-object pointers.  It didn't check for typlen\nbeing -1 first, which meant it could crash on fixed-length pass-by-ref\nvalues, and probably on cstring values as well.  It also didn't use\nDatumGetPointer before VARATT_IS_EXTERNAL_EXPANDED, which while currently\nharmless is not according to documentation nor prevailing style.\n\nI also think the lack of any explanation as to why datumSerialize makes\nthese particular nonobvious choices is pretty awful, so fix that.\n\nPer report from Jarred Ward.  Back-patch to 9.6 where this code came in.\n\nDiscussion: https://postgr.es/m/6F61E6D2-2F5E-4794-9479-A429BE1CEA4B@simple.com","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/9bf4068cc321a4d44ac54089ab651a49d89bb567"},{"sha":"13f03a001e4d841b6a27c0c9c3fe14e1fb2aad80","author":{"name":"Peter Eisentraut","email":"2f47089682e4afbd5de3eea4edffc95dfc1eb9de@gmx.net"},"message":"doc: Add missing pieces to logical replication protocol doc\n\nReported-by: Kyle Conroy <kyle@kyleconroy.com>","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/13f03a001e4d841b6a27c0c9c3fe14e1fb2aad80"}]}
{"actor":{"display_login":"postgres-mirror"}}