| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: -D option of pg_resetwal is only works with absolute path |
| Date: | 2018-05-23 15:40:48 |
| Message-ID: | 5c832332-ba16-3d7c-7a48-8d3aad08a255@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/23/18 11:35 AM, Tom Lane wrote:
> David Steele <david(at)pgmasters(dot)net> 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.
Looks good to me. Thanks!
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-05-23 16:25:20 | Re: Subplan result caching |
| Previous Message | Tom Lane | 2018-05-23 15:35:29 | Re: -D option of pg_resetwal is only works with absolute path |