Re: pg_ctl command option anomalies

From: Neha Khatri <nehakhatri5(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: pg_ctl command option anomalies
Date: 2017-04-20 06:05:45
Message-ID: CAFO0U+9SQAT2U0dS6NJ8rP+O1JTYe9XoGrdzh940qfdpom7T0w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

On Thu, Apr 20, 2017 at 3:53 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Neha Khatri <nehakhatri5(at)gmail(dot)com> writes:
> > Some of the pg_ctl modes do not require following options:
> > -m, -w, -t, -c, -l, -o, -p
>
> Um ... all of those except -c and -w require an argument AFAIK. Where did
> you read that they don't?

I did not mean that they don't require an argument. What I was trying to
refer is that "pg_ctl status" would not require a "-m fast", for instance.
Would there be a functional difference if I execute following commands:

pg_ctl status -D data/ -m fast
pg_ctl status -D data/ -m smart
pg_ctl status -D data/ -m immediate

If no, then -m does not seem a valid option for "pg_ctl status".But I am
allowed to execute all of the above.

Regards,
Neha

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Tom Lane 2017-04-20 06:20:40 Re: pg_ctl command option anomalies
Previous Message Tom Lane 2017-04-20 05:53:47 Re: pg_ctl command option anomalies