Deployment on Heroku about logidze

[palkan]

Logidze uses custom database variables (to conditionally track changes and responsible users) and thus requires superuser privileges (unless 9.6 haven't been released).

And Heroku doesn't provide superuser access (or other ways to alter databases or roles).

So, I had no idea how we can fix this for 9.5 so far. Sorry(
I need a little bit more time for investigation.

[nobodyzzz]

Face the same issue on Amazon RDS, as workaround use this:

require 'active_record/connection_adapters/postgresql_adapter'

ActiveRecord::ConnectionAdapters::PostgreSQLAdapter.set_callback :checkout, :after do
  execute("SELECT set_config('logidze.disabled', 'off', false)")
  execute("SELECT set_config('logidze.responsible', 'off', false)")
end

(Put to config/initializers/logidze_workaround.rb)

[palkan]

@nobodyzzz Thanks for the workaround! Added to the readme.

I just want to add that you still have to remove "ALTER DATABASE ..." statements from the installation migration.

[palkan]

@dedman
I've updated the gem (version 0.3.1), now should work on Heroku with PostgreSQL 9.6 without any tweak.

[dedman]

Thanks @palkan!

[Frexuz]

Then why is the alter database statements still in the generated migration template if it's not needed? 🤔
https://github.com/palkan/logidze/blob/master/lib/generators/logidze/install/templates/migration.rb.erb#L10

[palkan]

These statements are only included for PostgreSQL <9.6 where we need them (see #11 (comment))

[Frexuz]

Ah, my mistake :) Thanks