Craig Ringer <cr...@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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
