From: | mlw <pgsql(at)mohawksoft(dot)com> |
---|---|
To: | Oliver Elphick <olly(at)lfix(dot)co(dot)uk> |
Cc: | pgsql-hackers(at)postgresql(dot)org, pgsql-patchesr(at)postgresql(dot)org, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Subject: | Re: The last configuration file patch (I hope!) This one |
Date: | 2003-02-19 12:58:04 |
Message-ID: | 3E537F5C.5040301@mohawksoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Oliver Elphick wrote:
>On Wed, 2003-02-19 at 02:43, mlw wrote:
>
>
>>PostgreSQL Extended Configuration Patch
>>
>>
>...
>
>
>>--- Run-time process ID ---
>>postmaster -R /var/run/postmaster.pid
>>
>>This will direct PostgreSQL to write its process ID number
>>to a file, /var/run/postgresql.conf
>>
>>--- postgresql.conf options ---
>>
>>
>...
>
>
>>The "-R" option on the command line overrides the
>>"runtime_pidfile" in the configuration file.
>>
>>
>
>I raised the possibility of moving the pid file only last week. Tom
>pointed out that it acts as a lock on the database to prevent two
>postmasters' trying to manage the same database. As such it should NOT
>be a configurable parameter.
>
This is a different PID file. Sorry, this one is specifically for FHS
systems. The postmaster.pid file, as used by PostgreSQL remains in the
data directory.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-02-19 15:03:41 | Re: Performance Baseline Script |
Previous Message | Felipe Schnack | 2003-02-19 12:35:33 | psql problem in 7.2.3 |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-02-19 15:00:29 | Re: postgres error reporting |
Previous Message | Chisel Wright | 2003-02-19 11:52:39 | Re: postgres error reporting |