I’m testing out Axon with Postgres and it appears to leverage the Postgres Large Objects by default for its events and tokens. It appears that Postgres has disabled the access for large objects for non superuser accounts within Postgres 9.0. Now we’re currently using Postgres 9.6, and are seeing if there are workarounds for this.
I did some digging, and there is the lo_compat_privilege flag; however, that isn’t an option in our scenario to flip.
we decided not to do any workarounds in Axon for this matter. This is a “problem” that sits between Hibernate and Postgres, and we feel that customizing the mapping or table structure specifically to a database is a better solution than to complicate Axon with all kinds of database-specific variations of defaults.