From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_ctl reload -o "...." |
Date: | 2012-11-15 20:41:24 |
Message-ID: | CAMkU=1yGU+7JRK2x1E1p6NcsErTLveU2pBBnLmf_WTeCd9A1zg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Nov 15, 2012 at 11:26 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
>> Is there a reason pg_ctl reload shouldn't honor -o ?
>
> -o means "pass these switches on the postmaster's command line".
> If you're not restarting the postmaster, you don't get to change
> its command line.
OK. You see pg_ctl as a wrapper around postmaster, while I was
viewing it as a thing in itself.
> IMO setting stuff on the command line is pretty evil anyway.
I wouldn't do it in a production system, but it is invaluable for
performance testing during development or diagnosis.
Oh well, I guess this is what perl -i -pe is for.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Karl O. Pinc | 2012-11-15 20:53:24 | User control over psql error stream |
Previous Message | Alvaro Herrera | 2012-11-15 20:15:24 | Re: Timing events WIP v1 |