From: HaJo S. <ha...@ha...> - 2004-11-17 17:15:51
|
On Thu, 2004-11-18 at 00:53, Lionel Bouton wrote: > When disconnected SQLgrey tries to reconnect to the database but if it > fails it will exit. 1.1.3 was more robust in this respect because it > never retried immediately. But it had a bug which made it stop filtering > for as much as 24hours before trying to reconnect to the database. > I consider this a bug in 1.2.0 and 1.3.x, what I'll code is a more > tolerant behaviour in 1.2.1 to fix the problem (never exit) and redesign > 1.3 to sleep a little instead of trying to reconnect immediately (in > order to allow a temporary connection problem to go away) and refuse to > exit on DB errors too. Shame on me, I just discovered that sqlgrey is actually Perl and not binary -- that's what's happening in the RPM-age, I'm getting close to WIN... Just went briefly over the code and I also think that "or die" on DBI-Errors is probably not the thing one wants in a daemon. Maybe a sanity-connect&check when starting the daemon should be allowed to die, but after that I'd expect a daemon to stay alive whenever possible. I'm really worried about the situation where I'll bring postgresql down for a DB backup, upgrade or something. It'll take me min. a day to figure that sqlgrey has crashed and I'll likely loose mail that way. HaJo -- HaJo Schatz <ha...@ha...> http://www.HaJo.Net PGP-Key: http://www.hajo.net/hajonet/keys/pgpkey_hajo.txt |