Re: Usability, MySQL, Postgresql.org, gborg, contrib,

Поиск
Список
Период
Сортировка
От Joshua D. Drake
Тема Re: Usability, MySQL, Postgresql.org, gborg, contrib,
Дата
Msg-id 408EBF10.5030801@commandprompt.com
обсуждение исходный текст
Ответ на Re: Usability, MySQL, Postgresql.org, gborg, contrib,  (Andrew Dunstan <andrew@dunslane.net>)
Ответы Re: Usability, MySQL, Postgresql.org, gborg, contrib,  ("Jim C. Nasby" <jim@nasby.net>)
Re: Usability, MySQL, Postgresql.org, gborg, contrib,  (Andrew Dunstan <andrew@dunslane.net>)
Re: Usability, MySQL, Postgresql.org, gborg, contrib,  (Paul Tillotson <pntil@shentel.net>)
Re: Usability, MySQL, Postgresql.org, gborg, contrib,  (Gaetano Mendola <mendola@bigfoot.com>)
Список pgsql-hackers
>>  
>>
> 
> I know both. :-).
> 
> Seriously - I'd like to raise my voice in favor of installing plpgsql in 
> template1 by default. I haven't heard any good reason not to (nor even a 
> bad reason).
> 

If we install plPGSQL by default, we should install any other pl 
language that was configured at runtime by default as well. This 
includes plPerl, plTCL, and plPython.

Of course only if they were compiled in, but sense they are a part of 
the core distribution we shouldn't favor one over the other.

Personally, plpgSQL is only useful to those who are coming from Oracle.
People are more likely to be comfortable with plPython or plPerl than
plpgSQL.

Sincerely,

Joshua D. Drake



> cheers
> 
> andrew
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>      joining column's datatypes do not match


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: PITR Phase 2 - Design Planning
Следующее
От: Simon Riggs
Дата:
Сообщение: Re: PITR Phase 1 - Code Overview (1)