Re: [HACKERS] Make pg_regress print a connstring with sockdir - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Make pg_regress print a connstring with sockdir
Date
Msg-id 1824.1503920701@sss.pgh.pa.us
Whole thread Raw
In response to [HACKERS] Make pg_regress print a connstring with sockdir  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: [HACKERS] Make pg_regress print a connstring with sockdir  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
Craig Ringer <craig@2ndquadrant.com> writes:
> It's a pain having to find the postmaster command line to get the port
> pg_regress started a server on. We print the port in the pg_regress output,
> why not the socket directory / host?

I'm not following the point here.  The test postmaster isn't really
going to be around long enough to connect to it manually.  If you
want to do that, you should be using "installcheck", and then the
problem doesn't arise.

The reason for printing the port number, if memory serves, is to
aid in debugging port selection conflicts.  That doesn't really
apply for temporary socket directories; we're expecting libc to
avoid any conflicts there.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] 1 test fails in make installcheck-world - database "regress_ecpg_user2" does not exist
Next
From: Craig Ringer
Date:
Subject: Re: [HACKERS] Make pg_regress print a connstring with sockdir