Re: SQL code runs slower as a stored function - Mailing list pgsql-general

From S G
Subject Re: SQL code runs slower as a stored function
Date
Msg-id AANLkTikNjhMbY_aZiquHVg0C5AJRw6ZvrZxiYXBoqjy6@mail.gmail.com
Whole thread Raw
In response to Re: SQL code runs slower as a stored function  ("Greg Sabino Mullane" <greg@turnstep.com>)
List pgsql-general

I wrote a blog article about this: Google for "Why is my function slow?"

Greg, great article.  It's funny and humbling how I thought I'd invented the wheel with this workaround, but now it suddenly appears to be common practice.  I guess I'm on the right track.

I'm curious though-- your examples were plpgsql and you mentioned at the bottom that the plpgsql documentation mentions the one-time plan limitation.  Does the same hold true for stored functions in sql?  My slow function in this case is written in sql, so I'm guessing the answer is 'yes'.

pgsql-general by date:

Previous
From: Guillaume Lelarge
Date:
Subject: Re: pg_dumpall custom format?
Next
From: S G
Date:
Subject: Re: SQL code runs slower as a stored function