Re: pgsql: Improve error reporting when location specified by postgres -D d - Mailing list pgsql-committers

From Peter Eisentraut
Subject Re: pgsql: Improve error reporting when location specified by postgres -D d
Date
Msg-id 56B3FE06.4040903@gmx.net
Whole thread Raw
In response to Re: pgsql: Improve error reporting when location specified by postgres -D d  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On 2/2/16 11:26 PM, Tom Lane wrote:
> Peter Eisentraut <peter_e@gmx.net> writes:
>> +   if (configdir && stat(configdir, &stat_buf) != 0)
>> +   {
>> +       write_stderr("%s: could not access \"%s\": %s\n",
>> +                    progname,
>> +                    configdir,
>> +                    strerror(errno));
>
> Perhaps "could not access directory ..."?  This doesn't seem to follow the
> message style guideline about specifying what sort of object you're
> complaining about.

Done.

Somehow I was under the mistaken impression that one could also specific
a config file name there.



pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: pgsql: Improve error message
Next
From: Robert Haas
Date:
Subject: pgsql: When modifying a foreign table, initialize tableoid field proper