From: | Chapman Flack <chap(at)anastigmatix(dot)net> |
---|---|
To: | "Bossart, Nathan" <bossartn(at)amazon(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: improve CREATE EXTENSION error message |
Date: | 2021-11-29 22:31:04 |
Message-ID: | 61A554A8.804@anastigmatix.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11/29/21 17:13, Bossart, Nathan wrote:
> postgres=# CREATE EXTENSION does_not_exist;
> ERROR: extension "does_not_exist" is not available
> DETAIL: The extension must first be installed on the system where PostgreSQL is running.
> HINT: The pg_available_extensions view lists the extensions that are available for installation.
Messages crossed ...
If it were me, I would combine that DETAIL and HINT as one larger HINT,
and use DETAIL for specific details about what actually happened (such
as the exact filename sought and the %m).
The need for those details doesn't go away; they're still what you need
when what went wrong is some other freak occurrence the hint doesn't
explain.
Regards,
-Chap
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-11-29 22:42:03 | Re: improve CREATE EXTENSION error message |
Previous Message | Chapman Flack | 2021-11-29 22:24:12 | Re: improve CREATE EXTENSION error message |