| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | harding(dot)ian(at)gmail(dot)com |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: postmaster.pid |
| Date: | 2006-04-12 20:45:13 |
| Message-ID: | 4246.1144874713@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Ian Harding" <harding(dot)ian(at)gmail(dot)com> writes:
> The docs state that postmaster.pid is "A lock file recording the
> current postmaster PID and shared memory segment ID (not present after
> postmaster shutdown"
> I never looked until now, but I see the number 5432001 where the pid
> should be, and the real pid is in /tmp/.s.PGSQL.5432.lock, along with
> the path to data.
Not sure which PG version you are looking at, but in recent releases the
PID is on the first line, the second line is the $PGDATA path, and the
third has a couple of values associated with shared memory.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-04-12 20:50:59 | Re: "Hidden" field for each column |
| Previous Message | Tim Hart | 2006-04-12 19:54:08 | Evaluating client processes vs stored procedures |