From 0037cd1fa0f45c9a8545dcc16bdee7f71f94c773 Mon Sep 17 00:00:00 2001
From: Tim Graham <timograham@gmail.com>
Date: Tue, 10 Apr 2018 13:26:50 -0400
Subject: [PATCH] [1.11.x] Refs #28062 -- Doc'd PostgreSQL server-side cursors
 as a backwards incompatible change.

Backport of 2919a08c20d5ae48e381d6bd251d3b0d400d47d9 from master
---
 docs/releases/1.11.txt | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/docs/releases/1.11.txt b/docs/releases/1.11.txt
index 86a0fa53b5..7a01cba205 100644
--- a/docs/releases/1.11.txt
+++ b/docs/releases/1.11.txt
@@ -637,6 +637,17 @@ you must render model states using the ``clear_delayed_apps_cache()`` method as
 described in :ref:`writing your own migration operation
 <writing-your-own-migration-operation>`.
 
+Server-side cursors on PostgreSQL
+---------------------------------
+
+The change 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 (added in Django 1.11.1) in
+:setting:`DATABASES`.
+
+See :ref:`transaction-pooling-server-side-cursors` for more discussion.
+
 Miscellaneous
 -------------