| From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: improve CREATE EXTENSION error message |
| Date: | 2021-11-29 21:33:21 |
| Message-ID: | 1003AC46-48C0-4322-9499-3D01000304A3@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/29/21, 1:03 PM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> If we issue the hint only for errno == ENOENT, I think we could be
> less wishy-washy (and if it's not ENOENT, the hint is likely
> inappropriate anyway). I'm thinking something more like
>
> HINT: This means the extension is not installed on the system.
Good idea.
> I'm not quite satisfied with the "on the system" wording, but I'm
> not sure of what would be better. I agree that we can't just say
> "is not installed", because people will confuse that with whether
> it is installed within the database.
Right. The only other idea I have at the moment is to say something
like
This means the extension is not available[ on the system].
I don't know whether that is actually any less confusing, though.
Nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2021-11-29 21:33:49 | Re: Lots of memory allocated when reassigning Large Objects |
| Previous Message | Daniel Gustafsson | 2021-11-29 21:31:13 | Re: improve CREATE EXTENSION error message |