pgagroal_databases.conf
Limits for databases, users or both for pgagroal
- Provided by: pgagroal (Version: 2.1.0-1ubuntu1)
- Report a bug
Limits for databases, users or both for pgagroal
The pgagroal_databases.conf configuration file defines limits for a database or a user or both. It also supports database aliases, allowing clients to connect using alternative names for configured databases.
Database aliases allow clients to connect using alternative names for a configured database. This is useful for application migrations, multi-tenancy, or providing user-friendly names.
Aliases are specified in the DATABASE field using the format: database_name=alias1,alias2,alias3
When a client connects using an alias, pgagroal transparently maps it to the real database name for all backend operations.
# # DATABASE [=alias, alias, ...] USER MAX_SIZE INITIAL_SIZE MIN_SIZE # all all all production_db=prod,main myuser 10 5 2 development_db=dev,test,qa devuser 5 2 1 legacy_db legacyuser 8 3 1
In this example: - Clients can connect to "production_db", "prod", or "main" - all will use the same backend database - The development database has three aliases: "dev", "test", and "qa" - The legacy database has no aliases and uses the standard format
pgagroal is maintained on GitHub at <https://github.com/pgagroal/pgagroal>
pgagroal is licensed under the 3-clause BSD License.
pgagroal.conf(5), pgagroal_hba.conf(5), pgagroal_vault.conf(5), pgagroal(1), pgagroal-cli(1), pgagroal-admin(1), pgagroal-vault(1)