On Thu, 22 Mar 2001, Tom Lane wrote:
> What I see is a lot of
>
> ! psql: Backend startup failed
>
> which suggests a fork() failure. Look in the postmaster logfile to see
> the exact kernel error code --- but probably you are out of swap space
> or up against the kernel's limit on number of pr
On Thu, 22 Mar 2001, Peter Eisentraut wrote:
> 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.
Yes, it works now:
Justin Clift writes:
> 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?
I suppose things are a bit more complicate
Justin Clift <[EMAIL PROTECTED]> writes:
> 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 sha
Hey guys,
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 proble
Peter Eisentraut <[EMAIL PROTECTED]> 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
Alexander Klimov writes:
> Results of second and third passes are in the attachment.
> It is looks like failed tests are due to
> ! psql: connectDBStart() -- connect() failed: Connection refused
> ! Is the postmaster running locally
> ! and accepting connections on Unix socket '/tmp/.s.PG
Alexander Klimov <[EMAIL PROTECTED]> writes:
> It is looks like failed tests are due to
> ! psql: connectDBStart() -- connect() failed: Connection refused
> ! Is the postmaster running locally
> ! and accepting connections on Unix socket '/tmp/.s.PGSQL.65432'?
What I see is a lot of
! ps
