On Mon, Aug 28, 2017 at 7:57 AM, Craig Ringer wrote:
> I'm frequently debugging postmasters that are around long enough. Deadlocks,
> etc.
>
> It's also way easier to debug shmem related issues with a live postmaster vs
> a core.
Yeah. I don't *frequently* debug postmasters that hang during the
On 28 August 2017 at 19:45, Tom Lane wrote:
> Craig Ringer 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
Craig Ringer 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
Craig Ringer wrote:
> On 28 August 2017 at 15:19, Michael Paquier
> wrote:
>
> > On Mon, Aug 28, 2017 at 4:07 PM, Craig Ringer
> > wrote:
> > > == starting postmaster==
> > > running with PID 30235; connect with:
> > > psql "host='/tmp/pg_regress-j74
On 28 August 2017 at 15:19, Michael Paquier
wrote:
> On Mon, Aug 28, 2017 at 4:07 PM, Craig Ringer
> wrote:
> > == starting postmaster==
> > running with PID 30235; connect with:
> > psql "host='/tmp/pg_regress-j74yFE' port=50848 dbname='regression'"
On Mon, Aug 28, 2017 at 4:07 PM, Craig Ringer wrote:
> == starting postmaster==
> running with PID 30235; connect with:
> psql "host='/tmp/pg_regress-j74yFE' port=50848 dbname='regression'"
> == creating database "regression" ==
== 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
wrote:
On Mon, Aug 28, 2017 at 2:28 PM, Craig Ringer 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_reg
Hi all
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
