Re: [GENERAL] Warning: Don't delete those /tmp/.PGSQL.* files - Mailing list pgsql-hackers

From Larry Rosenman
Subject Re: [GENERAL] Warning: Don't delete those /tmp/.PGSQL.* files
Date
Msg-id 20001125164043.A14467@lerami.lerctr.org
Whole thread Raw
Responses Re: Re: [GENERAL] Warning: Don't delete those /tmp/.PGSQL.* files  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
* Tom Lane <tgl@sss.pgh.pa.us> [001125 16:37]:
> "Joel Burton" <jburton@scw.org> writes:
> 
> This story does indicate that we need a less fragile interlock against
> starting two postmasters on one database.  I have to admit that it
> hadn't occurred to me that you could break the port-number interlock
> so easily as that :-(.  But obviously you can, so we need a different
> way of representing the interlock.  Hackers, any thoughts?
how about a .pid/.port/.???  file in the /data directory, and a lock on that? 


-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 972-414-9812                 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749


pgsql-hackers by date:

Previous
From: Larry Rosenman
Date:
Subject: tcl/FreeBSD 4.2-STABLE, multiple TCL versions installed
Next
From: Bruce Momjian
Date:
Subject: Re: OK, that's one LOCALE bug report too many...