PostGIS and Posgresql search path

PostGIS and Posgresql search path

We recently added Geodjango and PostGIS to the system. I see that PosgGIS
installs itself in the public schema. Now, we are using PostgreSQL schemas
for client tenancy, so for example client A will have a schema tenant_A,
so we usually set the search path manually:
SET search_path TO tenant_A;
But since PostGIS lives inside the public schema, I will now have to do this:
SET search_path TO tenant_A, public;
Would it ever make sense to simply move the postGIS geometry_columns table
into the individual client schemas? The advantage of that would be 1)
clients' GIS data would have a greater degree of separation and 2)
Tenant-specific maintenance (backup, migrations, etc) would be easier.