Context Navigation

Changes between Version 7 and Version 8 of Ticket #35902, comment 1

v7	v8
7	7	To confirm the issue is not specific to `TEST_MIGRATE=False` yourself, try settings `MIGRATION_MODULES` entries to `None` for each of your `INSTALLED_APPS` and running `migrate --run-syncdb` against a fresh database, you should see the exact same failure.
8	8
9		Even if we wanted to only solve the problem for `TEST_MIGRATE=False` ~~the proposed solution~~ seems brittle as it requires the migrations to be fully applied on the non-test database (for extensions to exists and be introspected) which might the case for local development setups but definitely not the case on CI setups where only the test database is created.
	9	Even if we wanted to only solve the problem for `TEST_MIGRATE=False` [https://github.com/django/django/pull/18791 the proposed solution] seems brittle as it requires the migrations to be fully applied on the non-test database (for extensions to exists and be introspected) which might the case for local development setups but definitely not the case on CI setups where only the test database is created.
10	10
11	11	The best available options at this time for Postgres users running into this problem is to use the `TEST_TEMPLATE` [https://docs.djangoproject.com/en/5.1/ref/settings/#template database setting] to point it at a pre-configured database with extensions already installed on it.