Bruce Momjian wrote:
mlw wrote:
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 differe
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.con
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 ---
...
On Tue, 2003-02-18 at 21:43, mlw wrote:
> This patch enables PostgreSQL to be far more flexible in
> its configuration methodology.
Without weighing in on the configuration debate, one thing this patch
definitely needs to do is update the documentation.
Cheers,
Neil
--
Neil Conway <[EMAIL PROTE
PostgreSQL Extended Configuration Patch
Mohawk Software, 2003
This patch enables PostgreSQL to be far more flexible in
its configuration methodology.
Specifically, It adds two more command line parameters, "-C"
which specifies either the location of the postgres
configuration file or a directory co
