| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | ELOEHR(at)austin(dot)rr(dot)com |
| Cc: | t-ishii(at)sra(dot)co(dot)jp, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] postmaster.pid |
| Date: | 1999-12-04 03:02:44 |
| Message-ID: | 19991204120244P.t-ishii@sra.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > Note that even options execpt -S is not explicitly supplied in the
> > case above (postmaster -S), other opts are shown. This file is not
> > only convenient to restart postmaster but also is usefull to determin
> > with what defaults postmaster is running, IMHO.
>
> It's not quite clear to me: Do command line options override
> postmaster.opts options? (I would expect them to.)
No, postmaster.opts is just showing what options have been passed to
postmatser. Using it to determine what options should be given next
time is the job of pg_ctl which I'm writing now, not
postmaster's. Speaking about pg_ctl, probably I will give it the
ability to override postmaster.opts options.
--
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Veillard | 1999-12-04 14:09:54 | Re: [HACKERS] perl-DBD-Pg (was Re: BOUNCE pgsql-ports@postgreSQL.org: Non-member submission from[Joe Brenner <doom@kzsu.stanford.edu>] (fwd)) |
| Previous Message | Tatsuo Ishii | 1999-12-04 03:02:34 | Re: [HACKERS] postmaster.pid |