The db crashed again. I didn't have to restart the master nsd this time. Odd. I may not have had to restart the slave but ad_validate_security_info was spamming my error log ten times a second so I panicked and restarted it. :) But it looks like the driver was trying to reconnect to pg for each query while it started up. So the driver is exhonerated I think. :)
Here's what pg had to say in the log:
Jan 25 16:50:05 www logger: pq_recvbuf: unexpected EOF on client connection
Jan 25 16:50:05 www last message repeated 2 times
Jan 25 16:50:05 www logger: pq_flush: send() failed: Broken pipe
Jan 25 16:50:05 www logger: pq_recvbuf: unexpected EOF on client connection
Jan 25 16:50:05 www logger: pq_flush: send() failed: Broken pipe
Jan 25 16:50:05 www logger: pq_recvbuf: unexpected EOF on client connection
Jan 25 16:50:06 www logger: pq_flush: send() failed: Broken pipe
Jan 25 16:50:06 www logger: pq_recvbuf: unexpected EOF on client connection
Jan 25 16:50:06 www logger: pq_flush: send() failed: Broken pipe
Jan 25 16:50:06 www logger: pq_recvbuf: unexpected EOF on client connection
Jan 25 16:50:06 www logger: pq_flush: send() failed: Broken pipe
Jan 25 16:50:06 www logger: pq_recvbuf: unexpected EOF on client connection
Jan 25 16:50:11 www logger: Server process (pid 1476) exited with status 139 at
Fri Jan 25 16:50:11 2002
Jan 25 16:50:11 www logger: Terminating any active server processes...
Jan 25 16:50:11 www logger: NOTICE: Message from PostgreSQL backend:
Jan 25 16:50:11 www logger: ^IThe Postmaster has informed me that some other ba
ckend^Idied abnormally and possibly corrupted shared memory.
Jan 25 16:50:11 www logger: ^II have rolled back the current transaction and am
^Igoing to terminate your database system connection and exit.
