chore: refactor connection kill

Author: avallete

src/lib/db.ts

@@ -115,7 +115,12 @@ export const init: (config: PoolConfig) => {
         }
         return { data: res.rows, error: null }
       } catch (error: any) {
-        if (error.constructor.name === 'DatabaseError') {
+        if (
+          error.constructor.name === 'DatabaseError' &&
+          // If that's a global packet handling error it's raised as a "DatabaseError" but really is a
+          // underlying parser error, we want to error to be treated as a connection error and end the pool
+          !(error.message && error.message.startsWith('exception received while handling packet'))
+        ) {
           // Roughly based on:
           // - https://github.com/postgres/postgres/blob/fc4089f3c65a5f1b413a3299ba02b66a8e5e37d0/src/interfaces/libpq/fe-protocol3.c#L1018
           // - https://github.com/brianc/node-postgres/blob/b1a8947738ce0af004cb926f79829bb2abc64aa6/packages/pg/lib/native/query.js#L33