Re: Do we really want to migrate plproxy and citext into PG core distribution?
| От | Asko Oja |
|---|---|
| Тема | Re: Do we really want to migrate plproxy and citext into PG core distribution? |
| Дата | |
| Msg-id | ecd779860807242337y620a7b54s16cc9ed6f229d1bd@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Do we really want to migrate plproxy and citext into PG core distribution? (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Do we really want to migrate plproxy and citext into
PG core distribution?
Re: Do we really want to migrate plproxy and citext into PG core distribution? |
| Список | pgsql-hackers |
Hi
One of reasons to get PL/proxy into core is to make it available to Windows users also.
The idea is to get to the situation
createlang plproxy mydb
If we can achieve this without putting plproxy into core then i would like to hear how.
Asko
One of reasons to get PL/proxy into core is to make it available to Windows users also.
The idea is to get to the situation
createlang plproxy mydb
If we can achieve this without putting plproxy into core then i would like to hear how.
Asko
On Fri, Jul 25, 2008 at 2:19 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"Robert Haas" <robertmhaas@gmail.com> writes:You are merely setting up a straw man, as no one has suggested such a
> ISTM that if that if you're willing to admit, even with caveats, that
> PL/perl, PL/tcl, or PL/python doesn't "need" to be in core, then
> excluding anything else from core on the basis that it doesn't need to
> be there is silly.
policy. Any specific decision of this type is going to involve a
combination of factors, and that's only one.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: