Heroku db:push You may have encountered a bug in the Ruby interpreter or extension libraries.

[g-pavlik]

here's dump, I'll gladly give more information if needed https://gist.github.com/4052010

[will]

heroku db:push will soon be replaced with pg:push, which won't use taps, so wouldn't have this problem. It'll have all of its own, new problems! If you want a preview check out https://github.com/heroku/heroku-pg-extras/issues/42

[skull-squadron]

Probably can close this, as pg:push/:pull/etc. are already implemented.

Also, root cause of this issue could be an impedance mismatch between the native extensions on ruby interpreter version (1.9.3) and the rvm gemset version (1.8.7).

Also^2, just back/forthed someone at heroku, taps is mostly for use-cases where either one of the client/server is internet-accessible (not as secure, harder to work with corporate firewalls). This gem is still really useful for quick/dirty on-prem, on-network usage.