Re: confusing error message

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: confusing error message
Date: 2013-08-10 01:17:43
Message-ID: 520594B7.10303@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 08/10/2013 02:43 AM, Stephen Frost wrote:
> * Craig Ringer (craig(at)2ndquadrant(dot)com) wrote:
>> More seriously, with interpolated strings for relation names etc
>> it can be hard to know which chunks to search for, and search
>> engines aren't always good at having the whole message thrown at
>> them.
>
> It's not perfect, but if the searches are getting to mailing list
> archive messages then it's clearly possible for us to do better.
> Having an embedded code or URL or what-have-you might be an option
> too, but we need the documentation first in any case, so we could
> do these other things later..

Well said; you're quite right.

I complain myself that a focus on perfection can prevent progress.
Lets start with "helpful".

My first two would be:

"No pg_hba.conf entry for ..."

and

"fe_sendauth: no password supplied"

as both seem to confuse new users endlessly.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2013-08-10 02:39:01 killing pg_dump leaves backend process
Previous Message Josh Berkus 2013-08-09 23:29:00 Re: Proposal: leave a hint when switching logging away from stderr