Yeah, that's what we have to resort to now, but that's
not a solution. Until we kill the client, the entire
database is locked (or, at least the tables that other
clients need to write to, which is effectively the
same thing). This is annoying enough during the week
but it's especially a problem on weekends when none of
the developers are in the office.
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?
thanks,
Eugene
--- Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> On Tue, Jul 26, 2005 at 07:40:30AM -0700, Dr NoName
> wrote:
>
> > So, is transaction timeout option planned at all?
>
> > What's the alternative solution to a client that's
> hung in
> > transaction?
>
> Forcibly end it?
>
> --
> Alvaro Herrera (<alvherre[a]alvh.no-ip.org>)
> "I dream about dreams about dreams", sang the
> nightingale
> under the pale moon (Sandman)
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
