From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
---|---|
To: | Chapman Flack <chap(at)anastigmatix(dot)net>, Daniel Gustafsson <daniel(at)yesql(dot)se>, 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:47:09 |
Message-ID: | 74DC0613-009F-4208-B0D4-F307ED7CAB63@amazon.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11/29/21, 1:38 PM, "Chapman Flack" <chap(at)anastigmatix(dot)net> wrote:
> On 11/29/21 16:31, Daniel Gustafsson wrote:
>> That's a good point, the hint is targeting users who might not even know that
>> an extension needs to be physically and separately installed on the machine
>> before it can be installed in their database; so maybe using "installed" here
>> isn't entirely helpful at all. That being said I'm at a loss for a more
>> suitable word, "available" perhaps?
>
> Maybe a larger break with the "This means the extension something something"
> formulation, and more on the lines of
>
> HINT: an extension must first be present (for example, installed with a
> package manager) on the system where PostgreSQL is running.
I like this idea. I can do it this way in the next revision if others
agree.
Nathan
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-11-29 21:47:49 | Re: Lots of memory allocated when reassigning Large Objects |
Previous Message | Bossart, Nathan | 2021-11-29 21:39:14 | Re: improve CREATE EXTENSION error message |