Tom Lane wrote:
> Fair point, but you could make the same argument against *any* side
> effect of RESET CONNECTION. You're just complaining about PREPARE
> because you can see immediately where that breaks JDBC. Anything that
> any driver does to set up per-connection state the way it wants will
> be equally vulnerable.
Yes, exactly.
> Perhaps RESET CONNECTION should be a protocol-level operation instead
> of a SQL command? That would prevent user-level code from causing it
> without the driver knowing.
I just suggested as much in another email (our emails crossed).
-O