Should this be marked as volatile instead of stable
hixus opened this issue · comments
Should this be marked as volatile instead of stable? Noticed pr for similar issue in another implementation.
According to docs "Even a function with no side-effects needs to be labeled VOLATILE if its value can change within a single query; some examples are random(), currval(), timeofday()"
Hi @hixus :) absolutely! Thanks for taking the time and opening an issue. I will change it asap.
I changed and tested it, and it's now on the main branch available.