| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, Philip Warner <pjw(at)rhyme(dot)com(dot)au>, PostgreSQL HACKERS <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: fcntl(SETLK) [was Re: 2nd update on TOAST] |
| Date: | 2000-07-08 15:03:07 |
| Message-ID: | 200007081503.LAA11872@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> The other problem is a socket file left behind by a crashed postmaster. I
> don't consider this such a big problem; a crashed postmaster is not the
> normal mode of operation. The friendly message we have right now seems
> alright to me. And it's a way of tell that the postmaster crashed at all.
>
> One idea to get the pid in there somewhere is creating a socket file
> "/tmp/.s.PGSQL.port.pid" and making /tmp/.s.PGSQL.port a symlink to it.
> Then clients don't know the difference, but the server knows the pid and
> can take appropriate action. Or make the symlink the other way around, not
> sure.
The symlink is an interesting idea. lstat() on the normal name can give
the file name with pid.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-07-08 15:04:00 | Re: Re: postgres TODO |
| Previous Message | Vince Vielhaber | 2000-07-08 14:50:23 | Re: crypt and MD5 - still not wanted |