Re: Patch to add functionality to specify ORDER BY in CREATE FUNCTION for SRFs

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Atri Sharma <atri(dot)jiit(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch to add functionality to specify ORDER BY in CREATE FUNCTION for SRFs
Date: 2015-01-06 23:33:46
Message-ID: 54AC70DA.6030404@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1/6/15, 1:00 AM, Ashutosh Bapat wrote:
>
> Even checking whether the output of the function is in the right order or not, has its cost. I am suggesting that we can eliminate this cost as well. For example, PostgreSQL does not check whether a function is really immutable or not.

Actually, it does:

select test();
ERROR: UPDATE is not allowed in a non-volatile function
CONTEXT: SQL statement "UPDATE i SET i=i+1"
PL/pgSQL function test() line 3 at SQL statement
STATEMENT: select test();
ERROR: UPDATE is not allowed in a non-volatile function
CONTEXT: SQL statement "UPDATE i SET i=i+1"
PL/pgSQL function test() line 3 at SQL statement

--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kouhei Kaigai 2015-01-06 23:43:25 Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API)
Previous Message Petr Jelinek 2015-01-06 23:24:17 Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API)