Ron Williams

@dr-itz I updated the gem versions used in the main comment. I'll try and work on a simplified version of the migration for testing.

Full stack trace. Is there a way to make this not be horribly formatted? Here's the link to the raw [gist](https://gist.githubusercontent.com/rwilliams/2b7d2182e4f2de1beff61e66fd0d7cfd/raw/34467da6b12ddb0e305e8fe937a885a04b74e754/trace) ``` ➜ dcr web rails db:migrate --trace Starting cds_db_1...

well now it has no line endings...

I did a small data test and the only difference in the SQL was 'pg' uses BEGIN vs BEGIN TRANSACTION and COMMIT vs COMMIT TRANSACTION which makes no difference. I...

Here's sample log files from both [pg](https://github.com/jruby/activerecord-jdbc-adapter/files/3903323/pg.log) and [activerecord-jdbcpostgresql-adapter](https://github.com/jruby/activerecord-jdbc-adapter/files/3903322/jdbcpostgres.log). They are almost identical until the jdbc transaction rolls back for some reason. The only minor differences are in the insert...

So I created a [skeleton rails app](https://github.com/rwilliams/pg_test) to test this out with the following migration ``` class CreateTests < ActiveRecord::Migration[6.0] def change create_table :tests do |t| t.string :name t.string :profession...

@dr-itz What version of PG are you using. Also, did you check what `max_lock_per_transaction` was set at?

Awesome. Thanks, I imagine that speeds up execution quite a bit too?

I'm in the exact same situation. It would be sweet if we could add a root for the url in the auspice customisations.

theine_current_ruby doesn't get the current ruby, it runs theine with the current ruby. Both theine and theine_current_ruby expect some argument because it's essentially calling `rails`. Fixed in https://github.com/rwilliams/theine/commit/0c43e7924acabb255f405f826086c84b4dc45980