Re: pgsql: Remove function names from error messages

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Remove function names from error messages
Date: 2018-12-20 00:42:31
Message-ID: 13206.1545266551@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Michael Paquier <michael(at)paquier(dot)xyz> writes:
> On Wed, Dec 19, 2018 at 05:53:48PM +0000, Alvaro Herrera wrote:
>> Remove function names from error messages

> I am spotting a couple of extra ones for functions:
> src/backend/access/transam/xlog.c:
> (errmsg("pg_stop_backup cleanup done, waiting for required WAL segments
> to be archived")));
> src/backend/access/transam/xlog.c:
> (errmsg("pg_stop_backup still waiting for all required WAL segments to
> be archived (%d seconds elapsed)",

> Perhaps these could be improved as well?

Those are at least reporting SQL function names that the user will
recognize ... still, we don't normally localize error messages
by the reporting function name, so I tend to agree that these are
not following the style guide.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2018-12-20 01:21:45 Re: pgsql: Remove function names from error messages
Previous Message Michael Paquier 2018-12-19 23:41:03 Re: pgsql: Remove function names from error messages