Re: pgsql: Fix saving and restoring umask

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Fix saving and restoring umask
Date: 2017-09-23 14:17:26
Message-ID: 80186612-77fb-fce7-18b8-4842e466e918@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 9/22/17 17:48, Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>> Fix saving and restoring umask
>> In two cases, we set a different umask for some piece of code and
>> restore it afterwards. But if the contained code errors out, the umask
>> is not restored. So add TRY/CATCH blocks to fix that.
>
> Doesn't that need to be back-patched?

done

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2017-09-23 14:22:05 pgsql: Refactor new file permission handling
Previous Message Peter Eisentraut 2017-09-23 14:16:04 pgsql: Fix saving and restoring umask