On Tue, Jul 26, 2005 at 08:33:19AM -0700, Dr NoName wrote: > A single client should not be able to bring the entire > database down. The DB should recognize that the client > went down and roll back the transaction. That would be > the ideal solution. Anything else we can do to remedy > the situation? Now wait just a second. The database is not down at all just because somebody left a transaction open. The real problem is that that open transaction is having some resources locked, right? I guess the real answer is not to leave transactions open. If you do that by design, say because the app shows a data modification window, and keeps a transaction open just to be able to save the changes later, then you really need to rethink your app design. -- Alvaro Herrera (<alvherre[a]alvh.no-ip.org>) Maybe there's lots of data loss but the records of data loss are also lost. (Lincoln Yeoh) ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
