You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 10, 2019. It is now read-only.
When running a large data migration on our Rails app we received a cascade of postgreSQL related errors when running migrations in the after_release context as defined in .aptible.yml:
PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly,
PG::ConnectionBad: PQsocket() can't get socket descriptor: ROLLBACK * 2,
PG::ConnectionBad: PQsocket() can't get socket descriptor,
ActiveRecord::StatementInvalid: PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly,
cc: @fancyremarker
When running a large data migration on our Rails app we received a cascade of postgreSQL related errors when running migrations in the
after_releasecontext as defined in.aptible.yml:PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly,PG::ConnectionBad: PQsocket() can't get socket descriptor: ROLLBACK* 2,PG::ConnectionBad: PQsocket() can't get socket descriptor,ActiveRecord::StatementInvalid: PG::ConnectionBad: PQconsumeInput() server closed the connection unexpectedly,NoMethodError: undefined method 'result_error_field' for nil:NilClass(related to Rails' postgres adapter)The migration run failed in the same way twice. The migration was successful when ran manually via
aptible ssh rake db:migrate.