On 11/24/16 18:13, Robert Haas wrote: >> I'm finding hard to imagine a reason why these might be unsafe, but >> failed. I do notice they're all only used in information_schema. >> >> Could it just perhaps be that these just missed the verification >> process the other functions went through to determine their parallel >> safety? > Yes, I think that's it. I went through pg_proc.h, but never looked at > information_schema.sql.
This hasn't been fixed yet. It's easy to to, but taking a step back, - Is there any reason an immutable function (that is not lying about it) should be anything but parallel safe? - If so, could CREATE FUNCTION default it that way? - Maybe add a check to opr_sanity to make sure the default set of functions is configured the way we want? -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
