Horton

Re: GUC names in messages

Peter Smith <smithpb2250@gmail.com>

View thread View on postgr.es
From: Peter Smith <smithpb2250@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Peter Eisentraut <peter@eisentraut.org>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Nathan Bossart <nathandbossart@gmail.com>, Laurenz Albe <laurenz.albe@cybertec.at>, Tom Lane <tgl@sss.pgh.pa.us>, Daniel Gustafsson <daniel@yesql.se>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-10-11T02:25:05Z
Lists: pgsql-hackers 
On Wed, Oct 9, 2024 at 8:54 PM Michael Paquier <michael@paquier.xyz> wrote:
>
> Applied the previous patch after looking at it again.
> --
> Michael

AFAIK this brings my year-long "GUC names" thread to a conclusion.

Thanks, Michael for helping to get these last couple of patches
pushed, and thanks to everybody else who helped with the earlier ones.

I suspect there are plenty more "common" messages yet to be identified
but that can be a task for another thread.

This one is done.

======
Kind Regards,
Peter Smith.
Fujitsu Australia

Commits

  1. Apply GUC name from central table in more places of guc.c

  2. Use camel case for "DateStyle" in some error messages

  3. Unify some error messages to ease work of translators

  4. Apply more quoting to GUC names in messages

  5. Revise GUC names quoting in messages again

  6. doc: Mention how to use quotes with GUC names in error messages

  7. Apply quotes more consistently to GUC names in logs