jimmy/postgrest
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify in-database configuration example regarding IN DATABASE

Browse Source
This commit is contained in:
Wolfgang Walther
2022-01-08 22:25:31 +01:00
committed by Wolfgang Walther
parent 4bd090ba13
commit 737ad76dfd
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
configuration.rst
+3 -1
View File
@@ -76,9 +76,11 @@ For example, you can configure :ref:`db-schemas` and :ref:`jwt-secret` like this
.. code:: postgresql .. code:: postgresql
ALTER ROLE authenticator IN DATABASE <your_database_name> SET pgrst.db_schemas = "tenant1, tenant2, tenant3" ALTER ROLE authenticator SET pgrst.db_schemas = "tenant1, tenant2, tenant3"
ALTER ROLE authenticator IN DATABASE <your_database_name> SET pgrst.jwt_secret = "REALLYREALLYREALLYREALLYVERYSAFE" ALTER ROLE authenticator IN DATABASE <your_database_name> SET pgrst.jwt_secret = "REALLYREALLYREALLYREALLYVERYSAFE"
You can use both database-specific settings with `IN DATABASE` and cluster-wide settings without it. Database-specific settings will override cluster-wide settings if both are used for the same parameter.
Note that underscores(``_``) need to be used instead of dashes(``-``) for the in-database config parameters. Note that underscores(``_``) need to be used instead of dashes(``-``) for the in-database config parameters.
.. important:: .. important::