All of these operations are available from\nthe django.contrib.postgres.operations module.
You can create a PostgreSQL extension in your database using a migration file.\nThis example creates an hstore extension, but the same principles apply for\nother extensions.
\nSet up the hstore extension in PostgreSQL before the first CreateModel\nor AddField operation that involves\nHStoreField by adding a migration with\nthe HStoreExtension operation.\nFor example:
from django.contrib.postgres.operations import HStoreExtension\n\nclass Migration(migrations.Migration):\n ...\n\n operations = [\n HStoreExtension(),\n ...\n ]\nThe operation skips adding the extension if it already exists.
\nFor most extensions, this requires a database user with superuser privileges.\nIf the Django database user doesn’t have the appropriate privileges, you’ll\nhave to create the extension outside of Django migrations with a user that has\nthem. In that case, connect to your Django database and run the query\nCREATE EXTENSION IF NOT EXISTS hstore;.
CreateExtensionLink to this heading#An Operation subclass which installs a PostgreSQL extension. For common\nextensions, use one of the more specific subclasses below.
This is a required argument. The name of the extension to be installed.
\nBloomExtensionLink to this heading#Installs the bloom extension.
BtreeGinExtensionLink to this heading#Installs the btree_gin extension.
BtreeGistExtensionLink to this heading#Installs the btree_gist extension.
CITextExtensionLink to this heading#Installs the citext extension.
CryptoExtensionLink to this heading#Installs the pgcrypto extension.
HStoreExtensionLink to this heading#Installs the hstore extension and also sets up the connection to\ninterpret hstore data for possible use in subsequent migrations.
TrigramExtensionLink to this heading#Installs the pg_trgm extension.
UnaccentExtensionLink to this heading#Installs the unaccent extension.
If you need to filter or order a column using a particular collation that your\noperating system provides but PostgreSQL does not, you can manage collations in\nyour database using a migration file. These collations can then be used with\nthe db_collation parameter on CharField,\nTextField, and their subclasses.
For example, to create a collation for German phone book ordering:
\nfrom django.contrib.postgres.operations import CreateCollation\n\nclass Migration(migrations.Migration):\n ...\n\n operations = [\n CreateCollation(\n 'german_phonebook',\n provider='icu',\n locale='und-u-ks-level2',\n ),\n ...\n ]\nCreates a collation with the given name, locale and provider.
Set the deterministic parameter to False to create a\nnon-deterministic collation, such as for case-insensitive filtering.
Removes the collations named name.
When reversed this is creating a collation with the provided locale,\nprovider, and deterministic arguments. Therefore, locale is\nrequired to make this operation reversible.
PostgreSQL supports the CONCURRENTLY option to CREATE INDEX and\nDROP INDEX statements to add and remove indexes without locking out writes.\nThis option is useful for adding or removing an index in a live production\ndatabase.
Like AddIndex, but creates an\nindex with the CONCURRENTLY option. This has a few caveats to be aware\nof when using this option, see the PostgreSQL documentation of building\nindexes concurrently.
Like RemoveIndex, but removes the\nindex with the CONCURRENTLY option. This has a few caveats to be aware\nof when using this option, see the PostgreSQL documentation.