{"push_id":2302824276,"size":1,"distinct_size":1,"ref":"refs/heads/REL_10_STABLE","head":"34653bc9833d9c95ed1c52bed1ff01c6193de17b","before":"1597948c962a1407c01fc492c44917c097efa92e","commits":[{"sha":"34653bc9833d9c95ed1c52bed1ff01c6193de17b","author":{"name":"Tom Lane","email":"9ca635a44fdf5aa326758d8d245579b9ae84653c@sss.pgh.pa.us"},"message":"Be more wary about shm_toc_lookup failure.\n\nCommit 445dbd82a basically missed the point of commit d46633506,\nwhich was that we shouldn't allow shm_toc_lookup() failure to lead\nto a core dump or assertion crash, because the odds of such a\nfailure should never be considered negligible.  It's correct that\nwe can't expect the PARALLEL_KEY_ERROR_QUEUE TOC entry to be there\nif we have no workers.  But if we have no workers, we're not going\nto do anything in this function with the lookup result anyway,\nso let's just skip it.  That lets the code use the easy-to-prove-safe\nnoError=false case, rather than anything requiring effort to review.\n\nBack-patch to v10, like the previous commit.\n\nDiscussion: https://postgr.es/m/3647.1517601675@sss.pgh.pa.us","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/34653bc9833d9c95ed1c52bed1ff01c6193de17b"}]}
{"actor":{"display_login":"postgres-mirror"}}