From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Michael Glaesemann <grzm(at)seespotcode(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Modifying and solidifying contrib |
Date: | 2007-01-28 21:59:59 |
Message-ID: | 45BD1CDF.5010207@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>> I don't mind this term, BUT, what we need to get across is not just that
>> these are extensions, but that they are *standard* extensions, supplied
>> with PostgreSQL core code and supported by the PostgreSQL core team.
>> This would be analogous with, say, the standard perl modules (like
>> Exporter or IO::Handle) that come with the standard perl source
>> distribution. If we can get that idea across then we might lower the
>> resistance of people like hosting providers to loading them.
Furthering the perception is reality rule perhaps the schema should be
called std_ext?
>
> Integrating their docs into the standard PostgreSQL SGML (or XML,
> should we go there) docs would go a long, long way toward helping with
> this.
Agreed.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2007-01-28 22:02:04 | Re: Modifying and solidifying contrib |
Previous Message | Joshua D. Drake | 2007-01-28 21:58:38 | Re: Modifying and solidifying contrib |