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

From: David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: Patch to add functionality to specify ORDER BY in CREATE FUNCTION for SRFs
Date: 2015-01-06 07:31:24
Message-ID: CAKFQuwZaQcVeqiO8xKMD0VM4V0TuTEL8Z_SXbw1Vgwx5N79RTw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

>
> Best Wishes,
> Ashutosh Bapat
>
>
I imagine if it could be done reliably and cheaply the volatility
specifier would be checked. There are a number of situations where not
doing so confuses users and we get complaints. If we allow a constraint to
be specified we should try to error if that constraint is violated -
otherwise we probably should not allow it to be defined in the first place.

David J.

--
View this message in context: http://postgresql.nabble.com/Patch-to-add-functionality-to-specify-ORDER-BY-in-CREATE-FUNCTION-for-SRFs-tp5832876p5832988.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Kirkwood 2015-01-06 07:40:47 Re: Turning recovery.conf into GUCs
Previous Message Atri Sharma 2015-01-06 07:26:45 Re: Patch to add functionality to specify ORDER BY in CREATE FUNCTION for SRFs