pgAudit would do the trick (https://www.pgaudit.org/). If memory serves, you can specify a user to audit as well as the type of operations.
That said, if you are using migration scripts, it may be easier to just keep the scripts in version control with a sequential naming convention. Generally, these tools save state and know what has been applied.
We use liquibase to run migrations against our postgres 11 database. We run the migrations as an application user that does not have superuser permissions. Is there any workaround we could use that would allow us to capture the migration sql that is run by our application user? We want to capture all of the ddl as well as the dml run by the migration user. Since setting log_statement=all at the session level isn’t possible unless the user is a superuser is there any other way to accomplish this task?
