| From: | mlw <pgsql(at)mohawksoft(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Oliver Elphick <olly(at)lfix(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org, pgsql-patchesr(at)postgresql(dot)org |
| Subject: | Re: The last configuration file patch (I hope!) This one |
| Date: | 2003-02-19 23:27:47 |
| Message-ID: | 3E5412F3.9040506@mohawksoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | CoL | 2003-02-19 23:31:04 | Re: Hard problem with concurrency |
| Previous Message | Mike Aubury | 2003-02-19 23:16:00 | Re: request for sql3 compliance for the update command |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Naeslund(f) | 2003-02-19 23:32:33 | Re: pg_avd |
| Previous Message | Bruce Momjian | 2003-02-19 21:53:49 | Re: The last configuration file patch (I hope!) This one |