Re: Re: Clarifying "server starting" messaging in pg_ctl start without --wait

From: Ryan Murphy <ryanfmurphy(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Beena Emerson <memissemerson(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: Clarifying "server starting" messaging in pg_ctl start without --wait
Date: 2017-01-19 02:50:54
Message-ID: CAHeEsBdjs1Lp9Xhx0-KqjwLOmH43j-nKM8ay0Ug8gzcrkqKc5g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> The on-screen output isn't all that helpful for diagnosing what went
> wrong. You might learn more by looking at the regression.diffs files.
> Remember that errors tend to cascade, so the first one(s) in any
> particular test suite are the most important --- the rest might just
> be fallout.
>
>
Thanks Tom, I'll check out the diffs.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2017-01-19 03:09:23 Re: PoC: Grouped base relation
Previous Message Michael Paquier 2017-01-19 02:29:38 Re: Patch to implement pg_current_logfile() function