Re: simple functions, huge overhead, no cache - Mailing list pgsql-general

From Scott Ribe
Subject Re: simple functions, huge overhead, no cache
Date
Msg-id 86470CF1-A56C-4752-9E91-1A878215FF24@killerbytes.com
Whole thread Raw
In response to Re: simple functions, huge overhead, no cache  (Craig Ringer <craig@postnewspapers.com.au>)
List 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
manypeople 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@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice





pgsql-general by date:

Previous
From: "Daniel Verite"
Date:
Subject: Re: weird empty return from select problem; periodically get no data returned - could it be a network issue?
Next
From: Tom Lane
Date:
Subject: Re: simple functions, huge overhead, no cache