From: "Florian G. Pflug" <fgp@...>
Date: 2005-05-18T05:41:27+09:00
Subject: Re: ruby postgresql library: time out error

Pat Maddox wrote:
> That's a postgres problem, not a Ruby problem.  You said it takes
> nearly 20 minutes when using the command line client.  Don't you think
> that's a little excessive?  Actually, let me just inform you right now
> that it's a lot excessive.  Ruby times out because it says, "Uh,
> there's no reason it should be taking this long.  I quit."  And it's
> right, there's no reason it should take that long.
Actually, if you copy a few million rows, there is reason enough

> I don't know what the problem is, but it's a problem with your db, not
> Ruby.  There's probably a way to change the timeout in Ruby, so it
> would in fact wait that long.  I'd look to fix your db first though.
I'd say that its quite reasonable for _some_ statements to take
a long time - I'm running imports in a postgres database that
take a few hours, and don't time out. I'd probably not
want to call this from a webrequest, but it can still make sense ;-))

Which postgres module are you using? I'm using the (quite old)
binding for the pg-c-libs - There is a pure-ruby-implementation
too, which might inherit some ruby-specific socket-timeouts.

greetings, Florian Pflug