We have a legacy Rails 4.1 application running on Ubuntu 22.04 TLS (rbenv 1.2.0, ruby 2.1.10, pg gem 4.0.1, Postgres 10) that runs correctly, but Rake (12.3.3) and Rails c (when accessing ActiveRecord objects) consistently dump core with a segmentation fault at .rbenv/versions/2.1.10/lib/ruby/gems/2.1.0/gems/activerecord-4.0.1/lib/active_record/connection_adapters/postgresql_adapter.rb:831.
Rails log shows a successful migration run a few months ago and a few deprecation warnings (active record whitelist_attributes, fixed since then, and others not fixed but unrelated to database operations as far as we can tell).
Can anyone point to a possible cause of such behavioral divergence between Rails and Rake (or rails c when used to access ActiveRecord objects) if they’re both supposedly using the same activerecord gem?
Any help will be greatly appreciated.