  
  Transaction pooling and server-side cursors
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  
  Using a connection pooler in transaction pooling mode (e.g. `pgBouncer`_)
  requires disabling server-side cursors for that connection.
  
  Server-side cursors are local to a connection and remain open at the end of a
  transaction when :setting:`AUTOCOMMIT <DATABASE-AUTOCOMMIT>` is ``True``. A
  subsequent transaction may attempt to fetch more results from a server-side
 
</s> remove cursors on PostgreSQL prevents running Django with pgBouncer in transaction
 </s> add cursors on PostgreSQL prevents running Django with PgBouncer in transaction </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 .. _pgBouncer: https://pgbouncer.github.io/
 </s> add .. _PgBouncer: https://pgbouncer.github.io/ </s> remove pgBouncer
 </s> add PgBouncer
Using a connection pooler in transaction pooling mode (e.g. `PgBouncer`_)
  
  Transaction pooling and server-side cursors
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  
Using a connection pooler in transaction pooling mode (e.g. `PgBouncer`_)
  requires disabling server-side cursors for that connection.
  
  Server-side cursors are local to a connection and remain open at the end of a
  transaction when :setting:`AUTOCOMMIT <DATABASE-AUTOCOMMIT>` is ``True``. A
  subsequent transaction may attempt to fetch more results from a server-side
keep keep keep keep replace keep keep keep keep keep
 Corrected docs spelling of PgBouncer. 
docs/ref/databases.txt