Re: pgsql: Improve pg_ctl "cannot connect" warning, per suggestion from Mag - Mailing list pgsql-committers

From Bruce Momjian
Subject Re: pgsql: Improve pg_ctl "cannot connect" warning, per suggestion from Mag
Date
Msg-id 201011260347.oAQ3lYc24511@momjian.us
Whole thread Raw
In response to Re: pgsql: Improve pg_ctl "cannot connect" warning, per suggestion from Mag  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Improve pg_ctl "cannot connect" warning, per suggestion from Mag  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > Improve pg_ctl "cannot connect" warning, per suggestion from Magnus.
>
> Why does this string contain doubled spaces?

You mean two spaces after a semicolon?   Isn't that normal?  This is the
string:

                write_stderr(_("warning:  could not connect;  might be
            due to invalid authentication or\n"
                                "misconfiguration.\n"));

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

pgsql-committers by date:

Previous
From: itagaki@pgfoundry.org (User Itagaki)
Date:
Subject: textsearch-ja - textsearch_groonga: Released under PostgreSQL/BSD/MIT
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Improve pg_ctl "cannot connect" warning, per suggestion from Mag