Re: improve CREATE EXTENSION error message

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
Cc: Chapman Flack <chap(at)anastigmatix(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: improve CREATE EXTENSION error message
Date: 2021-11-29 21:49:16
Message-ID: 6EB9E47A-1329-4734-B489-2F0EDEB4824A@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 29 Nov 2021, at 22:47, Bossart, Nathan <bossartn(at)amazon(dot)com> wrote:
>
> 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.

I think taking it in this direction has merits.

--
Daniel Gustafsson https://vmware.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Guillaume Lelarge 2021-11-29 21:49:30 Re: Lots of memory allocated when reassigning Large Objects
Previous Message Tom Lane 2021-11-29 21:47:49 Re: Lots of memory allocated when reassigning Large Objects