Re: [HACKERS] The last configuration file patch (I hope!) This one
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 different PID file. Sorry, this one is specifically for FHS systems. The postmaster.pid file, as used by PostgreSQL remains in the data directory. Uh, how does this work if you don't do an FHS install --- where does it put this FHS postmaster.pid file? If there is no runtime_pidfile setting, (either in the configuration file or with "-R") no file is writen. ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] The last configuration file patch (I hope!) This one
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. ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] The last configuration file patch (I hope!) This one
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. -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight, UK http://www.lfix.co.uk/oliver GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C "And the angel answered and said unto the women, Fear ye not; for I know that ye seek Jesus, who was crucified. He is not here; for he is risen, as he said...Therefore be ye also ready; for in such an hour as ye think not the Son of man cometh." Matthew 28:5,6; 24:44 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] The last configuration file patch (I hope!) This one
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 PROTECTED]> || PGP Key ID: DB3C29FC ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
