Corrected docs spelling of PgBouncer.
This commit is contained in:
parent
1cdfe8d912
commit
b1f88476db
|
@ -206,7 +206,7 @@ cursor query is controlled with the `cursor_tuple_fraction`_ option.
|
||||||
Transaction pooling and server-side cursors
|
Transaction pooling and server-side cursors
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
Using a connection pooler in transaction pooling mode (e.g. `pgBouncer`_)
|
Using a connection pooler in transaction pooling mode (e.g. `PgBouncer`_)
|
||||||
requires disabling server-side cursors for that connection.
|
requires disabling server-side cursors for that connection.
|
||||||
|
|
||||||
Server-side cursors are local to a connection and remain open at the end of a
|
Server-side cursors are local to a connection and remain open at the end of a
|
||||||
|
@ -232,7 +232,7 @@ Another option is to wrap each ``QuerySet`` using server-side cursors in an
|
||||||
for the duration of the transaction. This way, the server-side cursor will only
|
for the duration of the transaction. This way, the server-side cursor will only
|
||||||
live for the duration of the transaction.
|
live for the duration of the transaction.
|
||||||
|
|
||||||
.. _pgBouncer: https://pgbouncer.github.io/
|
.. _PgBouncer: https://pgbouncer.github.io/
|
||||||
|
|
||||||
.. _manually-specified-autoincrement-pk:
|
.. _manually-specified-autoincrement-pk:
|
||||||
|
|
||||||
|
|
|
@ -10,7 +10,7 @@ Allowed disabling server-side cursors on PostgreSQL
|
||||||
===================================================
|
===================================================
|
||||||
|
|
||||||
The change in Django 1.11 to make :meth:`.QuerySet.iterator()` use server-side
|
The change in Django 1.11 to make :meth:`.QuerySet.iterator()` use server-side
|
||||||
cursors on PostgreSQL prevents running Django with pgBouncer in transaction
|
cursors on PostgreSQL prevents running Django with PgBouncer in transaction
|
||||||
pooling mode. To reallow that, use the :setting:`DISABLE_SERVER_SIDE_CURSORS
|
pooling mode. To reallow that, use the :setting:`DISABLE_SERVER_SIDE_CURSORS
|
||||||
<DATABASE-DISABLE_SERVER_SIDE_CURSORS>` setting in :setting:`DATABASES`.
|
<DATABASE-DISABLE_SERVER_SIDE_CURSORS>` setting in :setting:`DATABASES`.
|
||||||
|
|
||||||
|
|
|
@ -644,7 +644,7 @@ Server-side cursors on PostgreSQL
|
||||||
---------------------------------
|
---------------------------------
|
||||||
|
|
||||||
The change to make :meth:`.QuerySet.iterator()` use server-side cursors on
|
The change to make :meth:`.QuerySet.iterator()` use server-side cursors on
|
||||||
PostgreSQL prevents running Django with pgBouncer in transaction pooling mode.
|
PostgreSQL prevents running Django with PgBouncer in transaction pooling mode.
|
||||||
To reallow that, use the :setting:`DISABLE_SERVER_SIDE_CURSORS
|
To reallow that, use the :setting:`DISABLE_SERVER_SIDE_CURSORS
|
||||||
<DATABASE-DISABLE_SERVER_SIDE_CURSORS>` setting (added in Django 1.11.1) in
|
<DATABASE-DISABLE_SERVER_SIDE_CURSORS>` setting (added in Django 1.11.1) in
|
||||||
:setting:`DATABASES`.
|
:setting:`DATABASES`.
|
||||||
|
|
|
@ -446,7 +446,7 @@ permalink
|
||||||
pessimization
|
pessimization
|
||||||
Peucker
|
Peucker
|
||||||
pgAdmin
|
pgAdmin
|
||||||
pgBouncer
|
PgBouncer
|
||||||
PGRaster
|
PGRaster
|
||||||
phishing
|
phishing
|
||||||
php
|
php
|
||||||
|
|
Loading…
Reference in New Issue