In article <[EMAIL PROTECTED]>, Tom Lane <[EMAIL PROTECTED]> writes:
> One possible approach is to do the invalidation on a sufficiently coarse > grain that we don't care. For example, I would be inclined to make any > change in a table's schema invalidate all plans that use that table at > all; that would then subsume the constraint problem for instance. This > doesn't solve the inlined function problem however. How about using an even coarser grain? Whenever something in the database in question changes, blindly throw away all cached plans for this DB. ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
