From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: Proposed changes to security.html |
Date: | 2013-03-02 04:16:27 |
Message-ID: | 1362197787.11571.2.camel@vanquo.pezone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On Fri, 2013-03-01 at 16:22 -0800, Josh Berkus wrote:
> > What would be the point of that, other than introducing the use of less
> > accurate language?
>
> Oh, right, we have some contrib modules which are not extensions.
> However, the term "contrib" is confusing and not very helpful. Maybe I
> should use the term "Additional Supplied Modules" (shorthand "modules"),
> which is what we use in the docs?
That might be worthwhile consideration for introductory or marketing
material, say, but for the purpose of tracking security issues,
"contrib" is perfectly clear: If you are installing from source, it is
code that lives under contrib/. If you are installing from binary, it
is code that is in the postgresql-contrib package (usually). Calling it
anything other than "contrib" cannot possibly make that more clear.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-03-02 14:38:53 | Re: msgtxt.php archive links broken |
Previous Message | Magnus Hagander | 2013-03-02 04:10:37 | Re: msgtxt.php archive links broken |