| From: | "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: transaction idle timeout in 7.4.5 and 8.0.0beta2 |
| Date: | 2004-09-18 20:13:29 |
| Message-ID: | 20040918201329.GB90239@xs4all.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Sep 18, 2004 at 04:05:26PM -0400, Tom Lane wrote:
> Well, I think it would time out quickly --- anyway on the order of
> minutes not hours. By hypothesis, the situation you're worried about is
> where the backend was unable to send you a COMMIT acknowledgement
> message. The kernel is going to realize that it didn't get an ACK back,
> and is going to retry a few times, and is then going to declare the
> connection lost. The case where you may have a very long delay before
> detection of connection loss is where the backend is sitting idle with
> nothing to send.
That's one load off my mind, thanks.
Jeroen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Wheeler | 2004-09-18 20:22:50 | Re: libpq and prepared statements progress for 8.0 |
| Previous Message | Tom Lane | 2004-09-18 20:09:43 | Re: transaction idle timeout in 7.4.5 and 8.0.0beta2 |