Andrew Gierth <[EMAIL PROTECTED]> writes: > This is fairly obviously a simple consequence of the lack of plan > invalidation, it just happens to be more serious than most
Hmm, we plugged the correspoding hole on the SELECT side awhile back, but it seems that INSERT/UPDATE may need some defenses too. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers