| From: | Guyren Howe <guyren(at)gmail(dot)com> |
|---|---|
| To: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Immutable function WAY slower than Stable function? |
| Date: | 2018-08-07 16:57:15 |
| Message-ID: | 455A4B55-84BC-46A4-B1B7-F2F4246329A0@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Aug 7, 2018, at 9:10 , Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> I've had a to-do item to rewrite and improve the SQL function cache
> mechanism for a long time, but I hadn't thought it was high priority.
> Maybe it should be.
Personally, I would love this. Far too few developers dig into doing things in the database. Conceptually, doing all the data things in the database should be faster, more versatile, more secure etc.
Modern SQL has tools that can make its awfulness tolerable. CTEs and SQL functions spring immediately to mind. But both suffer from optimization fences and corner cases like this that arguably make it not worth the effort.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ken Tanzer | 2018-08-07 18:42:51 | Re: Immutable function WAY slower than Stable function? |
| Previous Message | Tom Lane | 2018-08-07 16:10:21 | Re: Immutable function WAY slower than Stable function? |