diff options
| author | Tim Graham <timograham@gmail.com> | 2018-04-10 13:26:50 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2018-04-10 13:27:06 -0400 |
| commit | 2e7b1e32976127bbe71320c848ce89b6e4b7e1a3 (patch) | |
| tree | 2747f37d084ad17edbcb40b50ef805494a6b5beb /docs | |
| parent | 7e5a72dde4ed9557aa180ee8aa0fd3915c8baa09 (diff) | |
[2.0.x] Refs #28062 -- Doc'd PostgreSQL server-side cursors as a backwards incompatible change.
Backport of 2919a08c20d5ae48e381d6bd251d3b0d400d47d9 from master
Diffstat (limited to 'docs')
| -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 ------------- |