| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Adding the extension name to EData / log_line_prefix |
| Date: | 2024-05-15 15:34:06 |
| Message-ID: | eb1c3195-8eb6-46c0-91be-44f2a79734c6@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 14.05.24 01:11, Tom Lane wrote:
> The mechanism that Andres describes for sourcing the name seems a bit
> overcomplex though. Why not just allow/require each extension to
> specify its name as a constant string? We could force the matter by
> redefining PG_MODULE_MAGIC as taking an argument:
>
> PG_MODULE_MAGIC("hstore");
We kind of already have something like this, for NLS. If you look for
pg_bindtextdomain(TEXTDOMAIN) and ereport_domain(), this information
already trickles into the vicinity of the error data. Maybe the same
thing could just be used for this, by wiring up the macros a bit
differently.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-05-15 15:46:34 | Re: CREATE TABLE creates a composite type corresponding to the table row, which is and is not there |
| Previous Message | Sriram RK | 2024-05-15 15:33:25 | Re: AIX support |