"Jeroen T. Vermeulen" <[EMAIL PROTECTED]> writes: > 1. Add a "soft" bit to prepared-statement plans > 2. Add rollback bookkeeping for prepared statements, which sets the bit > 3. Accept identical re-preparations of "soft" statements, clearing the bit
That sounds awfully ugly :-( It occurs to me that a lot of the problem would go away if we allowed DEALLOCATE of a nonexistent statement to not be an error (seems like a NOTICE would be be plenty). Then you could just unconditionally DEALLOCATE anything you were about to PREPARE, if you weren't entirely sure whether it already existed. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]