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

Specify external connection poolers

Browse Source
This commit is contained in:
laurenceisla
2021-09-30 17:18:58 -05:00
committed by GitHub
parent 09ca21d032
commit a6a088e9f0
3 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
admin.rst
+4 -4
View File
@@ -120,12 +120,12 @@ The burst argument tells Nginx to start dropping requests if more than five queu
Nginx rate limiting is general and indiscriminate. To rate limit each authenticated request individually you will need to add logic in a :ref:`Custom Validation <custom_validation>` function.
.. _connection_poolers:
.. _external_connection_poolers:
Using Connection Poolers
------------------------
Using External Connection Poolers
---------------------------------
In order to increase performance, PostgREST uses prepared statements by default. However, this setting is incompatible with connection poolers such as PgBouncer working in transaction pooling mode. In this case, you need to set the :ref:`db-prepared-statements` config option to ``false``. On the other hand, session pooling is fully compatible with PostgREST, while statement pooling is not compatible at all.
PostgREST manages its :ref:`own pool of connections <db-pool>` and uses prepared statements by default in order to increase performance. However, this setting is incompatible with external connection poolers such as PgBouncer working in transaction pooling mode. In this case, you need to set the :ref:`db-prepared-statements` config option to ``false``. On the other hand, session pooling is fully compatible with PostgREST, while statement pooling is not compatible at all.
.. note::
configuration.rst
+2 -2
View File
@@ -158,7 +158,7 @@ db-channel-enabled
When this is set to :code:`true`, the notification channel specified in :ref:`db-channel` is enabled.
You should set this to ``false`` when using PostgresSQL behind a connection pooler such as PgBouncer working in transaction pooling mode. See :ref:`this section <connection_poolers>` for more information.
You should set this to ``false`` when using PostgresSQL behind an external connection pooler such as PgBouncer working in transaction pooling mode. See :ref:`this section <external_connection_poolers>` for more information.
.. _db-prepared-statements:
@@ -169,7 +169,7 @@ db-prepared-statements
When disabled, the generated queries will be parameterized (invulnerable to SQL injection) but they will not be prepared (cached in the database session). Not using prepared statements will noticeably decrease performance, so it's recommended to always have this setting enabled.
You should only set this to ``false`` when using PostgresSQL behind a connection pooler such as PgBouncer working in transaction pooling mode. See :ref:`this section <connection_poolers>` for more information.
You should only set this to ``false`` when using PostgresSQL behind an external connection pooler such as PgBouncer working in transaction pooling mode. See :ref:`this section <external_connection_poolers>` for more information.
.. _db-tx-end:
releases/v8.0.0.rst
+1 -1
View File
@@ -28,7 +28,7 @@ Added
* Allow sending the header ``Prefer: headers-only`` to get a response with a ``Location`` header. See :ref:`insert_update`.
|br| -- `@laurenceisla <https://github.com/laurenceisla>`_
* Allow :ref:`connection_poolers` such as PgBouncer in transaction pooling mode.
* Allow :ref:`external_connection_poolers` such as PgBouncer in transaction pooling mode.
|br| -- `@laurenceisla <https://github.com/laurenceisla>`_
* Allow :ref:`config_reloading` by sending a SIGUSR2 signal.