| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "D(dot) S(dot)" <spider(at)skuggor(dot)se>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: unrecognized option '--help |
| Date: | 2015-05-22 06:13:07 |
| Message-ID: | CAB7nPqS6WaQHdiJR+E85couyxjkJsAATK13765b9Wso5fm44Xw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, May 22, 2015 at 11:24 AM, Tom Lane wrote:
> Meh. I don't particularly object to including --help in the switch set
> recognized in getopt_long ... but I doubt that that will actually fix
> Alvaro's scenario.
>
> Note that we should not rip out the existing code, because part of the
> reason for that is that it acts before any of the other stuff that runs
> before getopt parsing starts, eg the postmaster's refusal to run if you're
> root.
Well, this is true for postmaster and pg_ctl. By looking at
pg_resetxlog, pg_rewind and initdb the root check occurs after option
parsing.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-05-22 06:22:57 | Re: unrecognized option '--help |
| Previous Message | Alvaro Herrera | 2015-05-22 03:59:21 | Re: unrecognized option '--help |