| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | "Dave Page" <dpage(at)pgadmin(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Josh Berkus" <josh(at)agliodbs(dot)com>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
| Subject: | Re: Including PL/PgSQL by default |
| Date: | 2008-02-22 09:53:13 |
| Message-ID: | 200802221053.14357.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Am Freitag, 22. Februar 2008 schrieb Dave Page:
> I know I'm gonna regret wading in on this, but in my mind this is akin
> to one of the arguments for including tsearch in the core server -
> namely that too many brain dead hosting providers won't add a contrib
> module or anything else in a customer's database because they don't
> understand that just because it's not there by default doesn't mean
> it's in any way second rate. Including pl/pgsql in template1 will help
> those folks who forwhatever reason use such providers, whilst more
> savvy providers can easily disable it post-initdb if thats what they
> want to do.
Half of this entire thread is content-free because the participants are
apparently not aware that a database owner can add plpgsql *without*
superuser privileges.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2008-02-22 10:00:22 | Re: Including PL/PgSQL by default |
| Previous Message | Dave Page | 2008-02-22 07:53:18 | Re: Linking backend in one piece |