David Steele <[email protected]> writes: > On 5/23/18 10:08 AM, Tom Lane wrote: >> Seems to be caused by careless placement of new umask-changing code. >> I wonder how many other places that patch broke similarly.
> I'll look into this today.
I pushed a patch already, although certainly an additional pair of eyes
on the issue would be good.
regards, tom lane
