Known Issues

This page describes concerns, limitations to be considered when allocating resources for the a9s PostgreSQL plans, and other known issues.

Caveats

• Logical backups (PITR is disabled) use the tool pg_dumpall. This tool tries to acquire shared table locks. It waits 1 hour at most (by default) to get those locks. If it fails to acquire the lock within that amount of time, it will fail. A failed backup attempt will be repeated a few times before a backup is marked as failed.

Object Size Limit

a9s PostgreSQL has a hard tuple limit of 1 GB, however, storing anything above a few megabytes is discouraged. Anything bigger is decompressed in every backend, writes the same amount to WAL, blocks VACUUM, breaks logical replication slots, and can cause clients to run out of memory. For more information about this, please refer to the PostgreSQL limits documentation.