Discussion:
How to prevent from timeouts
Sebastian von Ulmenstein
2006-12-29 20:38:42 UTC
Permalink
Hi,

just like to know, if anybody of you found a way to prevent timeouts to
postgres.
I started with a timer, getting some data count every 30 seconds.
Now I found out, that any modal window stops the execution of the query
queue of pgsql4rb. The same happens with dialog boxes, alerts, etc.
If the user acts somehow slow in front of the screen he will be
disconnected.

Is there something I miss?
tcp_keepalives_idle (integer)
On systems that support the TCP_KEEPIDLE socket option, specifies the number
of seconds be-
tween sending keepalives on an otherwise idle connection. A value of 0 uses
the system default. If
TCP_KEEPIDLE is not supported, this parameter must be 0. This parameter is
ignored for connections
made via a Unix-domain socket.
No word about supported systems or the default. Anybody knows about this?

Thanks and regards
Sebastian
Aliacta Support
2006-12-29 23:15:02 UTC
Permalink
Hi Sebastian,

Try queuing a bogus or empty query from the modal window as soon as
it opens, it might resume the whole queue.

In RB modal windows stop all code execution by design. I've never
tried opening a modal window from within a thread though, which could
perhaps work around the problem too.

Happy New Year,

Marc
Post by Sebastian von Ulmenstein
Hi,
just like to know, if anybody of you found a way to prevent timeouts to
postgres.
I started with a timer, getting some data count every 30 seconds.
Now I found out, that any modal window stops the execution of the query
queue of pgsql4rb. The same happens with dialog boxes, alerts, etc.
If the user acts somehow slow in front of the screen he will be
disconnected.
Is there something I miss?
tcp_keepalives_idle (integer)
On systems that support the TCP_KEEPIDLE socket option, specifies the number
of seconds be-
tween sending keepalives on an otherwise idle connection. A value of 0 uses
the system default. If
TCP_KEEPIDLE is not supported, this parameter must be 0. This parameter is
ignored for connections
made via a Unix-domain socket.
No word about supported systems or the default. Anybody knows about this?
Loading...