| From: | Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Greg Sabino Mullane <htamfids(at)gmail(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Better title output for psql \dt \di etc. commands |
| Date: | 2025-02-04 19:03:21 |
| Message-ID: | 202502041903.tbp7krui4kq6@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2025-Feb-04, Tom Lane wrote:
> =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> > At this point I would just add a "translator:" comment that explains
> > that the ??? bit is for unexpected cases and can be translated in the
> > same way.
>
> Hmm, do we have a standard policy or comment wording about that?
> I looked for "translator: ... unexpected" and didn't find any
> existing comments of that sort.
I don't remember cases of messages of that kind marked for translation,
so I'm not surprised that we don't have any such comments. Those would
typically be elog() or the errfoo_internal() cases, I think.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"El sudor es la mejor cura para un pensamiento enfermo" (Bardia)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2025-02-04 19:23:28 | Re: Doc fix of aggressive vacuum threshold for multixact members storage |
| Previous Message | Matthias van de Meent | 2025-02-04 19:03:10 | Re: hash_search_with_hash_value is high in "perf top" on a replica |