From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Michael Glaesemann <grzm(at)seespotcode(dot)net>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Modifying and solidifying contrib |
Date: | 2007-01-28 21:44:54 |
Message-ID: | 20070128214454.GC32296@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Jan 28, 2007 at 04:52:27PM -0500, Andrew Dunstan wrote:
>
>
> Michael Glaesemann wrote:
> >
> >On Jan 28, 2007, at 11:25 , Joshua D. Drake wrote:
> >
> >>David Fetter wrote:
> >>>Not so great. SQL:2003 has a special meaning for the word "module."
> >>
> >>Yeah I saw mention of that in another thread, but I really didn't like
> >>the word plugins. Do you have another thought? Extensions?
> >
> >"Extensions" would tie in nicely with its common use in the docs,
> >especially wrt pgxs:
>
> 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.
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.
Cheers,
D
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter
Remember to vote!
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-01-28 21:49:50 | Re: weird buildfarm failures on arm/mipsel and --with-tcl |
Previous Message | David Fetter | 2007-01-28 21:22:35 | Re: Modifying and solidifying contrib |