On Mon, Apr 7, 2014 at 7:10 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Amit Kapila <amit.kapil...@gmail.com> writes: >> On Sat, Apr 5, 2014 at 8:24 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > AFAICS, pg_ctl already reports to stderr if stderr is a tty. This whole > issue only comes up when pg_ctl itself is running as a service (which > I guess primarily means starting/stopping the postgresql service?). > So that puts extra weight on trying to be sure that error messages go > to a predictable place; the user's going to be hard-pressed to debug > background failures without that.
Agreed. I think if this needs to fixed, then it will be better to do as per your suggestion of adding a new switch. So I have marked this patch as "Returned with feedback". With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
