Django-pgclone

Feature

- Django 5.0 compatibility [Wesley Kendall, cd279dd]

Support and test against Django 5 with psycopg2 and psycopg3.

Trivial

- Added Opus10 branding to docs [Wesley Kendall, ba4621f]

Feature

- Add Python3.12 support and use Mkdocs for documentation [Wesley Kendall, 97e7d99]

Python 3.12 and Postgres 16 are supported now, along with having revamped docs using Mkdocs
and the Material theme.

Python 3.7 support was dropped.

Feature

- Added Python 3.11, Django 4.2, and Psycopg 3 support [Wesley Kendall, d1cf98c]

Adds Python 3.11, Django 4.2, and Psycopg 3 support along with tests for multiple Postgres versions. Drops support for Django 2.2.

Api-Break

- Changed behavior of reversible restores and local copies [Wes Kendall, de428c1]

Using the ``--reversible`` option for ``pgclone restore`` is now only applicable to
database dumps and no longer has any effect when executed against a local database.
The aliases used by reversible restores have also changed from ``previous`` and
``current`` to ``pre`` and ``post``.

In other words, if one uses ``--reversible`` during a ``pgclone restore`` of
a database dump, one can revert back to the version of data pre-restore using
``pgclone restore :pre`` or the version of the data immediately after
the restore using ``pgclone restore :post``.

Unlike before, running ``pgclone restore :pre`` or ``pgclone restore :post`` has
no effect on the copies created when restoring a dump using ``--reversible``.
The ``:pre`` and ``:post`` aliases are only changed when a new reversible dump
is restored.

This same behavior applies to local copies too. ``pclone copy`` now requires
a target name in the format of a local dump key (``:db_name``), and the special
``:pre`` and ``:post`` aliases cannot be used. Users can do
``pgclone copy :my_backup`` and ``pgclone restore :my_backup`` without affecting
the special snapshots related to the last restore from a dump.

Feature

- Support overriding Postgres statement timeouts [Wes Kendall, 4ef38f4]

Use ``settings.PGCLONE_STATEMENT_TIMEOUT`` to override Postgres's
``statement_timeout`` setting when running core ``pgclone`` SQL operations such
as ``CREATE DATABASE``.

You can also use ``settings.PGCLONE_LOCK_TIMEOUT`` to override Postgres's
``lock_timeout`` setting.