Database migration operations¶
All of these operations are available from
Creating extension using migrations¶
You can create a PostgreSQL extension in your database using a migration file. This example creates an hstore extension, but the same principles apply for other extensions.
from django.contrib.postgres.operations import HStoreExtension class Migration(migrations.Migration): ... operations = [ HStoreExtension(), ... ]
Django checks that the extension already exists in the database and skips the migration if so.
For most extensions, this requires a database user with superuser privileges.
If the Django database user doesn’t have the appropriate privileges, you’ll
have to create the extension outside of Django migrations with a user that has
them. In that case, connect to your Django database and run the query
CREATE EXTENSION IF NOT EXISTS hstore;.
In older versions, the existence of an extension isn’t checked.
hstoreextension and also sets up the connection to interpret hstore data for possible use in subsequent migrations.
Index concurrent operations¶
PostgreSQL supports the
CONCURRENTLY option to
CREATE INDEX and
DROP INDEX statements to add and remove indexes without locking out writes.
This option is useful for adding or removing an index in a live production
AddIndex, but creates an index with the
CONCURRENTLYoption. This has a few caveats to be aware of when using this option, see the PostgreSQL documentation of building indexes concurrently.
CONCURRENTLY option is not supported inside a transaction (see