From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: improve CREATE EXTENSION error message |
Date: | 2021-11-29 20:32:20 |
Message-ID: | C5E91D75-CCD8-47D3-A874-BDB82A88629E@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 29 Nov 2021, at 20:54, Bossart, Nathan <bossartn(at)amazon(dot)com> wrote:
>
> Hi hackers,
>
> Currently, if you attempt to use CREATE EXTENSION for an extension
> that is not installed, you'll see something like the following:
>
> postgres=# CREATE EXTENSION does_not_exist;
> ERROR: could not open extension control file "/usr/local/pgsql/share/extension/does_not_exist.control": No such file or directory
>
> I suspect this ERROR message is confusing for novice users, so perhaps
> we should add a HINT. With the attached patch, you'd see the
> following:
>
> postgres=# CREATE EXTENSION does_not_exist;
> ERROR: could not open extension control file "/usr/local/pgsql/share/extension/does_not_exist.control": No such file or directory
> HINT: This typically indicates that the specified extension is not installed on the system.
>
> Thoughts?
I haven't given the suggested wording too much thought, but in general that
sounds like a good idea.
--
Daniel Gustafsson https://vmware.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-11-29 20:56:28 | Re: Correct handling of blank/commented lines in PSQL interactive-mode history |
Previous Message | Rémi Lapeyre | 2021-11-29 20:26:48 | Re: Commitfest 2021-11 Patch Triage - Part 2 |