Re: Adding the extension name to EData / log_line_prefix - Mailing list pgsql-hackers

From Chapman Flack
Subject Re: Adding the extension name to EData / log_line_prefix
Date
Msg-id 6644F7DE.9050704@acm.org
Whole thread Raw
In response to Re: Adding the extension name to EData / log_line_prefix  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 05/15/24 13:45, Tom Lane wrote:
> if we tell people to write
> 
>    PG_MODULE_MAGIC;
>    #undef TEXTDOMAIN
>    #define TEXTDOMAIN PG_TEXTDOMAIN("hstore")
> 
> then that's 100% backwards compatible and they don't need any
> version-testing ifdef's.

OT for this thread, but related: supposing out-of-core extensions
participate increasingly in NLS, would they really want to use
the PG_TEXTDOMAIN macro?

That munges the supplied domain name with PG's major version and
.so version numbers.

Were such versioning wanted for an out-of-core extension's message
catalogs, wouldn't the extension's own versioning be better suited?

Regards,
-Chap




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Adding the extension name to EData / log_line_prefix
Next
From: Robert Haas
Date:
Subject: Re: psql JSON output format