On 05/27/2017 09:50 PM, Peter Eisentraut wrote:
On 5/25/17 12:30, Konstantin Knizhnik wrote:
Functions like (info->>'name') are named "surjective" ni mathematics.
A surjective function is one where each value in the output type can be
obtained by some input value. That's not what you are after here. The
behavior you are describing is a not-injective function.
I think you are right that in practice most functions are not injective.
But I think there is still quite some difference between a function
like the one you showed that selects a component from a composite data
structure and, for example, round(), where in practice any update is
likely to change the result of the function.
Thank you, I will rename "surjective" parameter to "injective" with "false" as
Concerning "round" and other similar functions - obviously there are use cases
when such functions are used for
functional indexes. This is why I want to allow user to make a choice and this
is the reason of introducing this parameter.
The question is the default value of this parameter: should we by default
preserve original Postgres behavior:
check only affected set of keys or should we pay extra cost for calculating
value of the function (even if we managed to store
calculated value of the indexes expression for new tuple, we still have to
calculate it for old tuple, so function will be calculated
at least twice more times).
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
Sent via pgsql-hackers mailing list (firstname.lastname@example.org)
To make changes to your subscription: