  
  .. warning::
  
      In addition to the changes outlined in this section, be sure to review the
      :doc:`deprecation timeline </internals/deprecation>` for any features that
      have been removed. If you haven't updated your code within the
      deprecation timeline for a given feature, its removal may appear as a
      backwards incompatible change.
  
  Database backend API
  ~~~~~~~~~~~~~~~~~~~~
  
  * A couple of new tests rely on the ability of the backend to introspect column
 
</s> remove Database backends
^^^^^^^^^^^^^^^^^

* The PostgreSQL backend (``django.db.backends.postgresql_psycopg2``) is also
  available as ``django.db.backends.postgresql``. The old name will continue to
  be available for backwards compatibility.

 </s> add  </s> remove If you fail to do so, Django 1.9 and 2.0 will perform the conversion like
earlier versions but emit a deprecation warning. Django 2.0 won't perform any
 </s> add If you fail to do so, the conversion will be performed as in earlier versions
(with a deprecation warning) up until Django 1.11. Django 2.0 won't perform any </s> remove 1.8 or older versions. We've :ref:`dropped some features
<deprecation-removed-in-1.9>` that have reached the end of their deprecation
cycle, and we've `begun the deprecation process for some features`_.
 </s> add 1.8 or older versions. We've :ref:`dropped some features<removed-features-1.9>`
that have reached the end of their deprecation cycle, and we've `begun the
deprecation process for some features`_. </s> remove .. removed-features-1.9:
 </s> add .. _removed-features-1.9: </s> remove   cells has changed from ``(None)`` (or its translated equivalent) to ``-``.
 </s> add   cells has changed from ``(None)`` (or its translated equivalent) to ``-`` (a
  dash).
    :ref:`removed-features-1.9` for the features that have reached the end of
    their deprecation cycle and therefore been removed. If you haven't updated
    your code within the deprecation timeline for a given feature, its removal
    may appear as a backwards incompatible change.
  
  .. warning::
  
      In addition to the changes outlined in this section, be sure to review the
    :ref:`removed-features-1.9` for the features that have reached the end of
    their deprecation cycle and therefore been removed. If you haven't updated
    your code within the deprecation timeline for a given feature, its removal
    may appear as a backwards incompatible change.
    :ref:`removed-features-1.9` for the features that have reached the end of
    their deprecation cycle and therefore been removed. If you haven't updated
    your code within the deprecation timeline for a given feature, its removal
    may appear as a backwards incompatible change.
    :ref:`removed-features-1.9` for the features that have reached the end of
    their deprecation cycle and therefore been removed. If you haven't updated
    your code within the deprecation timeline for a given feature, its removal
    may appear as a backwards incompatible change.
    :ref:`removed-features-1.9` for the features that have reached the end of
    their deprecation cycle and therefore been removed. If you haven't updated
    your code within the deprecation timeline for a given feature, its removal
    may appear as a backwards incompatible change.
  
  Database backend API
  ~~~~~~~~~~~~~~~~~~~~
  
  * A couple of new tests rely on the ability of the backend to introspect column
keep keep keep keep replace replace replace replace keep keep keep keep keep
 Alphabetized a few sections in the 1.9 release notes + made a few tweaks. 
docs/releases/1.9.txt