Hang in PGconn#block while waiting for PGconn#async_exec about ruby-pg HOT 8 CLOSED

Original comment by Michael Granger (Bitbucket: ged, GitHub: ged).

a gdb trace of [the] issue: https://gist.github.com/04198029379211128b32

from ruby-pg.

Original comment by vangberg (Bitbucket: vangberg, GitHub: vangberg).

This is happening in my rack applications served by Nginx/Passenger 3.0.7, like the issue reported on sequel-talk, fwiw.

from ruby-pg.

Original comment by Anonymous.

Any news on this?

from ruby-pg.

Original comment by Michael Granger (Bitbucket: ged, GitHub: ged).

I haven't seen the hang myself since I started using 0.11.0 with the patch in <<changeset 3d744d9776c3>>, but of course it's difficult to tell if it's actually fixed or not since I don't have a way to reliably reproduce it. I'm doing an extensive reorganization of the build system at the moment, but once I have that sorted, I'll release 0.11.1 with the aforementioned fix.

from ruby-pg.

Original comment by Michael Granger (Bitbucket: ged, GitHub: ged).

I'm still testing what I think is a fix for this issue (<<changeset 17a6a01c1725>>, committed as a part of <<issue 66>>'s fix). So far, I haven't had any hangs, but I could use some confirmation if any of you are willing to try out hg tip.

from ruby-pg.

Original comment by jmileham (Bitbucket: jmileham, GitHub: jmileham).

Hi Michael,

I can confirm that this fix works for me.

I have a Heroku environment that was reproducing 100% of the time (making diagnosis of the root cause difficult). After discovering this thread and cutting a prerelease gem I am now getting appropriate error messages instead of hangs.

from ruby-pg.

Original comment by Michael Granger (Bitbucket: ged, GitHub: ged).

Thanks, @jmileham! It's still working for me as well, so I'll go ahead and release.

from ruby-pg.

Original comment by Anonymous.

This issue – or something similar to it – may not have been completely solved. See https://github.com/DatabaseCleaner/database_cleaner/issues/371 (and my log there) for more information. Not sure though where the problem lies, but there's clearly an async_exec there, too for me and it hangs forever.

from ruby-pg.