  Allowed disabling server-side cursors on PostgreSQL
  ===================================================
  
  The change in Django 1.11 to make :meth:`.QuerySet.iterator()` use server-side
  cursors on PostgreSQL prevents running Django with pgBouncer in transaction
  pooling mode. To reallow that, use the :setting:`DISABLE_SERVER_SIDE_CURSORS
  <DATABASE-DISABLE_SERVER_SIDE_CURSORS>` setting in :setting:`DATABASES`.
  
  See :ref:`transaction-pooling-server-side-cursors` for more discussion.
  
 
</s> remove PostgreSQL prevents running Django with pgBouncer in transaction pooling mode.
 </s> add PostgreSQL prevents running Django with PgBouncer in transaction pooling mode. </s> remove Using a connection pooler in transaction pooling mode (e.g. `pgBouncer`_)
 </s> add Using a connection pooler in transaction pooling mode (e.g. `PgBouncer`_) </s> remove .. _pgBouncer: https://pgbouncer.github.io/
 </s> add .. _PgBouncer: https://pgbouncer.github.io/ </s> remove pgBouncer
 </s> add PgBouncer
cursors on PostgreSQL prevents running Django with PgBouncer in transaction
  Allowed disabling server-side cursors on PostgreSQL
  ===================================================
  
  The change in Django 1.11 to make :meth:`.QuerySet.iterator()` use server-side
cursors on PostgreSQL prevents running Django with PgBouncer in transaction
  pooling mode. To reallow that, use the :setting:`DISABLE_SERVER_SIDE_CURSORS
  <DATABASE-DISABLE_SERVER_SIDE_CURSORS>` setting in :setting:`DATABASES`.
  
  See :ref:`transaction-pooling-server-side-cursors` for more discussion.
  
keep keep keep keep replace keep keep keep keep keep
 Corrected docs spelling of PgBouncer. 
docs/releases/1.11.1.txt