Re: GUC names in messages - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: GUC names in messages
Date
Msg-id 00b8d030-15cb-4609-b34a-98519b4c4c3b@eisentraut.org
Whole thread Raw
In response to Re: GUC names in messages  (Michael Paquier <michael@paquier.xyz>)
Responses Re: GUC names in messages
List pgsql-hackers
On 30.11.23 06:59, Michael Paquier wrote:
>               ereport(elevel,
>                       (errcode(ERRCODE_UNDEFINED_OBJECT),
> -                     errmsg("unrecognized configuration parameter \"%s\" in file \"%s\" line %d",
> -                            item->name,
> +            /* translator: %s%s%s is for an optionally quoted GUC name */
> +                     errmsg("unrecognized configuration parameter %s%s%s in file \"%s\" line %d",
> +                            GUC_FORMAT(item->name),
>                               item->filename, item->sourceline)));

I think this is completely over-engineered and wrong.  If we start down 
this road, then the next person is going to start engineering some rules 
by which we should quote file names and other things.  Which will lead 
to more confusion, not less.  The whole point of this quoting thing is 
that you do it all the time or not, not dynamically based on what's 
inside of it.

The original version of this string (and similar ones) seems the most 
correct, simple, and useful one to me.




pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Refactoring backend fork+exec code
Next
From: Nathan Bossart
Date:
Subject: postgres_fdw test timeouts