| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | 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:34:19 |
| Message-ID: | 0444b276-a7c3-57fe-0b5a-04928aed177c@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/23/18 10:08 AM, Tom Lane wrote:
> tushar <tushar(dot)ahuja(at)enterprisedb(dot)com> writes:
>> In the latest PG v11, found that -D option of pg_resetwal is only
>> works with absolute path .. not with relative path
>
> Confirmed here. This did work in previous releases, so I'd say it's
> unquestionably a bug.
>
> [ diffs v10 against head... ]
>
> 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.
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-05-23 15:35:29 | Re: -D option of pg_resetwal is only works with absolute path |
| Previous Message | Tom Lane | 2018-05-23 15:20:24 | Re: A Japanese-unfriendy error message contruction |