ruby – ActiveRecord：当连接断开时如何自动重新连接到PostgreS

ActiveRecord的:: Base.verify_active_connections！已经在2012年的rails commit 9d1f1b1ea9e5d637984fda4f276db77ffd1dbdcb中删除了.所以我们不能使用那种方法.

以下句子是我的简短调查结果.我不是rails activerecord的专家.所以要谨慎听. (但希望这有帮助)

comment in connection_pool.rb说

# 1. Simply use ActiveRecord::Base.connection as with Active Record 2.1 and
  #    earlier (pre-connection-pooling). Eventually,when you're done with
  #    the connection(s) and wish it to be returned to the pool,you call
  #    ActiveRecord::Base.clear_active_connections!. This will be the
  #    default behavior for Active Record when used in conjunction with
  #    Action Pack's request handling cycle.

所以也许你(和我有同样的情况就像你一样)必须返回池连接.

并作为Action Pack的请求处理周期返回sinatra中池的连接,使用ActiveRecord :: ConnectionAdapters :: ConnectionManagement

use ActiveRecord::ConnectionAdapters::ConnectionManagement

然后如rails commit 9d1f1b1ea9e5d637984fda4f276db77ffd1dbdcb中所述,我们使用与this line中不同的方式,当通过遵守动作包生命周期使用Basae.connection时始终checkout_and_verify.

def connection
    # this is correctly done double-checked locking
    # (ThreadSafe::Cache's lookups have volatile semantics)
    @reserved_connections[current_connection_id] || synchronize do
      @reserved_connections[current_connection_id] ||= checkout
    end
  end