H
Han Holl
Hi,
I'm using drb for a Postgres database connection pool, and to avoid problems
with premature garbage collection, I return the result array itself, rather
than a proxy PGresult object.
If the generated result is larger than the @load_limit, the client raises
an exception (drb.rb:107:in `load': too large packet 37106545) , but the
server is keeps waiting (as a rather large process, I might add).
This might be because I use unix domain sockets, rather than TCP/IP.
Wouldn't it make sense to generate this exception in the server? The client
would then automatically be notified.
Cheers,
Han Holl
I'm using drb for a Postgres database connection pool, and to avoid problems
with premature garbage collection, I return the result array itself, rather
than a proxy PGresult object.
If the generated result is larger than the @load_limit, the client raises
an exception (drb.rb:107:in `load': too large packet 37106545) , but the
server is keeps waiting (as a rather large process, I might add).
This might be because I use unix domain sockets, rather than TCP/IP.
Wouldn't it make sense to generate this exception in the server? The client
would then automatically be notified.
Cheers,
Han Holl