Re: [GENERAL] Warning: Don't delete those /tmp/.PGSQL.* files

From: Larry Rosenman <ler(at)lerctr(dot)org>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [GENERAL] Warning: Don't delete those /tmp/.PGSQL.* files
Date: 2000-11-25 22:40:43
Message-ID: 20001125164043.A14467@lerami.lerctr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

* Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> [001125 16:37]:
> "Joel Burton" <jburton(at)scw(dot)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(at)lerctr(dot)org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message GH 2000-11-25 23:03:27 Re: Warning: Don't delete those /tmp/.PGSQL.* files
Previous Message Tom Lane 2000-11-25 22:35:13 Re: Warning: Don't delete those /tmp/.PGSQL.* files

Browse pgsql-hackers by date

  From Date Subject
Next Message GH 2000-11-25 23:03:27 Re: Warning: Don't delete those /tmp/.PGSQL.* files
Previous Message Tom Lane 2000-11-25 22:35:13 Re: Warning: Don't delete those /tmp/.PGSQL.* files