AMQ 7, with JDBC persistence, will try to guess the kind of SQL dialect to use by querying the JDBC driver.

However, some databases ought to work with AMQ 7, but do not provide responses that fall within the broker's narrow test constraints. For example, EnterpriseDB, which is a variant of Postgres, does not identify itself in a way that allows the broker to treat it as Postgres.

I think all that's required is a simple configuration property.