| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net> |
| 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:35:29 |
| Message-ID: | 5877.1527089729@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2018-05-23 15:40:48 | Re: -D option of pg_resetwal is only works with absolute path |
| Previous Message | David Steele | 2018-05-23 15:34:19 | Re: -D option of pg_resetwal is only works with absolute path |