| From: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>, Martin Pitt <martin(at)piware(dot)de> |
| Subject: | Re: stopping server does not remove external_pid_file |
| Date: | 2006-06-07 23:09:49 |
| Message-ID: | 20060607230949.GA1429@timbira.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Tom Lane wrote:
> No, because the external pidfile has zero to do with Postgres' internal
> behavior.
>
+1. So we have two options: have external_pid_file mimics the internal
behavior or deprecates it.
I couldn't find the discussion about it; just the patch [1]. IIRC this
'feature' was proposed to permit another home to postmaster.pid file. Am
I wrong? But seems to duplicate the pid file information.
[1] http://archives.postgresql.org/pgsql-patches/2004-06/msg00006.php
--
Euler Taveira de Oliveira
http://www.timbira.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Cruz | 2006-06-07 23:56:22 | length checking and encoding in postgresql 8.1.4 |
| Previous Message | Jim C. Nasby | 2006-06-07 23:04:24 | Re: stopping server does not remove external_pid_file |