Ok, so now it's using Pgstatus, interesting. Any thoughts on why I see so many TIME_WAIT connections to my database?
I have usually around 150-170 at all times. My timeout is the Linux default of 4 min. Am I just the lucky one, or do others see this? I'm using 2.0.6 on a Linux Gentoo box, kernel 2.6.12 and a very recent glibc. I'm only bothered by it, because it seems like it indicates a potential problem and I'd rather find it first before it finds me. Thanks. -- David A. Niblett | email: [EMAIL PROTECTED] Network Administrator | Phone: (352) 334-3400 Gainesville Regional Utilities | Web: http://www.gru.net/ -----Original Message----- From: Paul J Stevens [mailto:[EMAIL PROTECTED] Sent: Monday, September 19, 2005 7:52 AM To: DBMail mailinglist Subject: Re: [Dbmail] 2.0.6+ DB Keepalive Niblett, David A wrote: > Paul, > > I believe you mentioned that in 2.0.6 and above, dbmail now opens a > new connection to the database every second to make sure that it's > alive rather than using the pgstatus function. (for PostgreSQL) before 2.0.6 it called db_connect/db_disconnect every second or so. Now it calls db_check_connection in stead, which calls PQstatus for postgres. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ Dbmail mailing list Dbmail@dbmail.org https://mailman.fastxs.nl/mailman/listinfo/dbmail
