From: | Michael Fuhr <mike(at)fuhr(dot)org> |
---|---|
To: | Dr NoName <spamacct11(at)yahoo(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: transaction timeout |
Date: | 2005-07-26 15:35:27 |
Message-ID: | 20050726153526.GA76297@winnie.fuhr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Jul 26, 2005 at 07:40:30AM -0700, Dr NoName wrote:
>
> I have been quite satisfied with the level of support
> from the PostgreSQL community, but this time I'm
> getting nothing.
There have been a couple of replies to your post, although perhaps
not what you were hoping for:
http://archives.postgresql.org/pgsql-general/2005-07/msg00984.php
http://archives.postgresql.org/pgsql-general/2005-07/msg00985.php
> So, is transaction timeout option planned at all?
A search through the archives shows that transaction timeout has
been discussed recently in pgsql-hackers, but unless I've missed
something it it hasn't been implemented yet (and therefore probably
won't be available in 8.1 since it's in feature freeze).
> What's the alternative solution to a client that's hung in transaction?
What's the client doing that takes locks strong enough to "lock up
the entire database"? Why does the client hang? Since the database
doesn't currently have a way to detect and handle these situations,
it might be worthwhile to find out what's happening to see if it
can be prevented.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2005-07-26 15:37:04 | Re: transaction timeout |
Previous Message | Luke Lonergan | 2005-07-26 15:33:34 | Re: [Bizgres-general] Hardware suggestions for a new data |