Comment by jstrong

can't believe postgres still uses a process-per-connection model that leads to endless problems like this one.