Known Limitations

There are a few known limitations.

• We do not support the "Enterprise" version of EDB PostgreSQL at this time, but have started looking into what it would take to be able to do so.

  In preliminary testing with the "Standard" version of EDB PostgreSQL, our plugin works. We will be doing more thorough internal validation on this version.

• Certain kinds of SQL statements (such as CREATE TABLE foo AS select ...) produce multiple auditing records. This cannot be disabled due to the way PostgreSQL itself invokes various internal hooks.

• The plugin cannot determine the accessed object for certain statements:

  • CREATE MATERIALIZED VIEW

  • CREATE SCHEMA when no schema name is supplied. (The SQL syntax allows this in certain cases.)

  • DROP CAST

• When logging to a file, records are flushed when the standard I/O buffer fills up and/or when the session ends.

• Attempting to install a plugin compiled for one major version of PostgreSQL on another will fail. PostgreSQL 9.3 and later print a "version mismatch" message to the start-up log. In such a case the database will not come up.

  Version 9.2 of PostgreSQL also will fail to load a mismatched plugin and also will not start up.

  This is a limitation of PostgreSQL.