Re: [HACKERS] postmaster locking issues. - Mailing list pgsql-hackers

From Thomas G. Lockhart
Subject Re: [HACKERS] postmaster locking issues.
Date
Msg-id 36219ED2.A5C19DDC@alumni.caltech.edu
Whole thread Raw
Responses Re: [HACKERS] postmaster locking issues.  (Bruce Momjian <maillist@candle.pha.pa.us>)
Re: [HACKERS] postmaster locking issues.  ("Marc G. Fournier" <scrappy@hub.org>)
List pgsql-hackers
> >> 5.  The port lock will be kept in '/var/opt/pgsql/lock/'.

As everyone has pointed out, we can't count on a specific convention for
where the lock file should go. However, we can probably count on a
convention to be followed on a particular OS. That would seem to be
something to define in Makefile.port, which could then be overridden by
a configure option or Makefile.custom entry.

On my RedHat Linux systems, the appropriate place seems to be /var/lock
or /var/lock/pgsql.

                        - Tom

pgsql-hackers by date:

Previous
From: "Thomas G. Lockhart"
Date:
Subject: Re: [HACKERS] Open 6.4 items
Next
From: "Thomas G. Lockhart"
Date:
Subject: Re: [HACKERS] Parser breakage: "timestamp" has become a reserved word