From: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
---|---|
To: | Ed Loehr <ELOEHR(at)austin(dot)rr(dot)com> |
Cc: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] postmaster.pid |
Date: | 1999-12-03 16:51:59 |
Message-ID: | 3847F52F.51258299@wgcr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Ed Loehr wrote:
> Tatsuo Ishii wrote:
> > Another file "postmaster.opts" is also created under $PGDATA. It
> > contains the path to postmaster and each option for postmaster per
> > line. Example contents are shown below:
[snip]
> > 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.)
>From what I gather from Tatsuo's message, the 'postmaster.opts' file
only shows the status of the currently running postmaster -- IOW, it's
not a configuration file, but a status indicator.
And I like the idea of this status information being available in this
way.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 1999-12-03 16:54:21 | emacs question |
Previous Message | Lamar Owen | 1999-12-03 16:43:53 | Re: [Fwd: postgresql-6.5.3. RPMs (Well Done!)] |