From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Make pg_regress print a connstring with sockdir |
Date: | 2017-08-28 07:07:47 |
Message-ID: | CAMsr+YEC+0d1P=HJupHYfs90zm4KSpSH817ut7mfvMa6tuLHbQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
============== starting postmaster ==============
running with PID 30235; connect with:
psql "host='/tmp/pg_regress-j74yFE' port=50848 dbname='regression'"
============== creating database "regression" ==============
On 28 August 2017 at 14:08, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
wrote:
> On Mon, Aug 28, 2017 at 2:28 PM, Craig Ringer <craig(at)2ndquadrant(dot)com>
> wrote:
> > 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?
> >
> > How about
> > running on 'port=50848 host=/tmp/pg_regress-UMrcT3' with PID 16409
> >
> > per the attached?
> >
> > If you'd prefer nicer wording at the expense of two lines, maybe
> >
> > running with PID 16409
> > connection string: 'port=50848 host=/tmp/blah'
>
> Yeah, I think that this is a good idea.
> --
> Michael
>
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
Attachment | Content-Type | Size |
---|---|---|
v2-0001-Show-sockdir-hostname-in-pg_regress-startup-outpu.patch | text/x-patch | 990 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Rajkumar Raghuwanshi | 2017-08-28 07:14:15 | Re: advanced partition matching algorithm for partition-wise join |
Previous Message | yangjie@highgo.com | 2017-08-28 07:05:37 | Re: hash partitioning based on v10Beta2 |