>> 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/
---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
