beickhof@xxxxxxxxxxx writes: > Well, I am considering a function that does select from a table, but the > table contents change extremely infrequently (the table is practically a > list of constants). Would it be safe to declare the function IMMUTABLE > provided that the table itself is endowed with a trigger that will drop > and recreate the function any time the table contents are modified? What you'd want to do is restart all existing sessions so that any plans made using precomputed function values are discarded. The trigger you suggest is fairly pointless because it will not cause regeneration of plans. I concur with Bill's remark that you should first determine if there's a really substantial benefit to marking the function immutable rather than merely stable. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
