Re: Unix Domain Sockets error (was Re: [HACKERS] Alpha initdb fixed!) - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Unix Domain Sockets error (was Re: [HACKERS] Alpha initdb fixed!)
Date
Msg-id 199803171452.JAA13555@candle.pha.pa.us
Whole thread Raw
In response to Unix Domain Sockets error (was Re: [HACKERS] Alpha initdb fixed!)  ("Pedro J. Lobo" <pjlobo@euitt.upm.es>)
Responses Re: Unix Domain Sockets error (was Re: [HACKERS] Alpha initdb fixed!)
Re: Unix Domain Sockets error (was Re: [HACKERS] Alpha initdb fixed!)
List pgsql-hackers
> I've done more tests. The problem is that if you start the postmaster
> without the '-p' option and without assigning a value to the PGPORT
> environment variable, then all the ipc stuff is messed up. No shared
> memory regions are created, and the semaphores are created but never
> freed. When a port number is specified, the sempahores (and the shared
> memory regions) have a 'key' value that contains the port number. Without
> port number, there is no shared memory and the sempahores have 0 as the
> key value.
>
> I don't know if this behaviour is due to the use of a non-standard port
> (5440), but since it's been specified in configure (--with-pgport=5440) it
> should work. shouldn't it?
>
> These are the regression tests when a port number is specified (note that
> you *must* assign a value to PGPORT before running the tests):

Let's get a patch for this alpha fix.  Not sure about the pgport problem.

--
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Re: [PATCHES] patches for 6.2.1p6
Next
From: Bruce Momjian
Date:
Subject: Re: Unix Domain Sockets error (was Re: [HACKERS] Alpha initdb fixed!)