3.0 SQL pooling question

In 3.0, is there a way to consider a SQL connection dead if it returns a certain class of errors, then close and re-open it? We had a problem overnight with postgres and query-planner caching for long-lived connections. Since we "do ITIL" (sigh) I have to write the problem up and submit a "possible solutions". If 3.0 can handle that for us, I can put that down as a "planned" item.