diff options
| author | Tim Graham <timograham@gmail.com> | 2018-04-10 13:26:50 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-04-10 13:26:50 -0400 |
| commit | 2919a08c20d5ae48e381d6bd251d3b0d400d47d9 (patch) | |
| tree | ec43d96a899074d009b6761ac2884ad44cad8cd8 /docs/releases | |
| parent | 9d7e2c7b447b2bbabe746770ebd26465cc564f05 (diff) | |
Refs #28062 -- Doc'd PostgreSQL server-side cursors as a backwards incompatible change.
Diffstat (limited to 'docs/releases')
| -rw-r--r-- | docs/releases/1.11.txt | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/docs/releases/1.11.txt b/docs/releases/1.11.txt index 1803a3ae62..ddcfaafa3a 100644 --- a/docs/releases/1.11.txt +++ b/docs/releases/1.11.txt @@ -640,6 +640,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 ------------- |