I don't understand what you mean by "This will avoid using Unix domain
sockets, which are broken on Solaris.".
If this were the case, then the errors which are described would happen
on ALL solaris platforms wouldn't they? And other packages using Unix
domain sockets would have problems too wouldn't they?
If it's of any help, I get the same types of regression testing failures
on Solaris, with the same "is the backend running?" type error
messages.. when the installation of solaris HAS NOT had it's /etc/system
file altered to change the amount of shared memory segments and
Whenever I have those problems, I insert the updated (higher) values for
shared memory and semaphores, reboot the system, then the tests pass as
the backend is able to start fine.
Hope this is helpful.
Regards and best wishes,
Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > In src/test/regress/pg_regress[.sh], line 163, change
> > *-*-qnx* | *beos*)
> > to
> > *-*-qnx* | *beos* | *solaris*)
> > and rerun the tests. This will avoid using Unix domain sockets, which are
> > broken on Solaris.
> I was just thinking that maybe pg_regress should have a command line
> option to set unix_sockets=no, so that both connection options could
> be exercised when there's doubt.
> regards, tom lane
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2001-03-22 23:27:01|
|Subject: Re: Tests randomly failed |
|Previous:||From: Tom Lane||Date: 2001-03-22 20:41:13|
|Subject: Re: psql -c tends to core dump if interrupted |