From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
---|---|
To: | "Trewern, Ben" <Ben(dot)Trewern(at)mowlem(dot)com> |
Cc: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Speed of different procedural language |
Date: | 2005-12-22 13:29:53 |
Message-ID: | 6EE64EF3AB31D5448D0007DD34EEB3417DDBAE@Herge.rcsinc.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Tom Lane wrote:
> I'd expect plpgsql to suck at purely computational tasks, compared to
> the other PLs, but to win at tasks involving database access. These
There you go...pl/pgsql is pretty much required learning (it's not
hard). For classic data processing tasks, it is without peer. I would
generalize that a large majority of tasks fall under this category.
pl/pgsql is quick, has a low memory profile, and you can cut sql
directly in code instead of through a proxy object...I could go on and
on about how useful and important that is.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Schaber | 2005-12-22 13:34:16 | Re: MySQL is faster than PgSQL but a large margin in |
Previous Message | Szűcs Gábor | 2005-12-22 12:52:44 | Re: Wrong index used when ORDER BY LIMIT 1 |