id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
36694	PostGIS backend silently ignores most Index options when targeting a single GeometryField (expressions, condition, include, opclasses)	Luciano de la Iglesia	Clifford Gama	"I have this model:

{{{
class Foo(models.Model):
    location = geomodels.PointField(geography=True, spatial_index=False)
    is_current = models.BooleanField()

    class Meta:
        indexes = [
            GistIndex(fields=[""location""], condition=Q(is_current=True), name=""current_foo""),
        ]
}}}
When I create the migration, the sql for my current_foo index is:

{{{
CREATE INDEX ""current_foo"" ON ""webatds_foo"" USING GIST (""location"");
}}}
This ignores my condition, I expect it to be:
{{{
CREATE INDEX ""current_foo"" ON ""webatds_foo"" USING GIST (""location"") where is_current=true;
}}}
I'm using django 5.2.7, psycopg 3.2.12, and PostGIS 17.3.5."	Bug	assigned	GIS	5.2	Normal		postgis index condition include		Accepted	1	0	0	0	0	0