| From: | Scott Ribe <scott_ribe(at)killerbytes(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | Postgres General Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: simple functions, huge overhead, no cache |
| Date: | 2010-07-10 14:52:27 |
| Message-ID: | 86470CF1-A56C-4752-9E91-1A878215FF24@killerbytes.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
This may need to be made more obvious in the documentation...
Having both SQL and PL/PgSQL languages is one of those things that is different enough from other database systems that many people will not expect and may not notice it unless it is pointed out explicitly and prominently.
On Jul 10, 2010, at 1:07 AM, Craig Ringer wrote:
> For such simple expressions, you should use 'SQL' functions. These can
> often be inlined to allow the query planner to avoid call overheads
> entirely, and are WAY cheaper even if they can't be inlined. They're
> less flexible, but much faster.
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
http://www.elevated-dev.com/
(303) 722-0567 voice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-07-10 15:48:29 | Re: simple functions, huge overhead, no cache |
| Previous Message | Daniel Verite | 2010-07-10 09:42:44 | Re: weird empty return from select problem; periodically get no data returned - could it be a network issue? |