In article <6028(dot)1110785150(at)sss(dot)pgh(dot)pa(dot)us>,
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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 making this even more coarse-grained? Blindly throw all
cached plans away when something in the database DDL changes.