There are a number of cases where the EXTENSION for postGIS is created iwth a schema qualifier.
CREATE SCHEMA postgis;
CREATE EXTENSION PostGIS WITH SCHEMA postgis;
why is that? what are the tradeoffs in using the schema?
PostGIS Schema Qualifier – Best Practices
postgispostgresql
Related Question
- PostgreSQL PostGIS – Copying Schema with Geometry Column
- Postgresql – How to create a copy of postgis db from one windows machine to another
- PostgreSQL – How to Initialize PostGIS Database in Single-User Mode
- PostgreSQL PostGIS – Installing in a Different Schema Causes Topology Extension to Not Find Geometry Type
- PostGIS Migration – Common Problems and Solutions
- PostgreSQL – How to Use pg_restore with Different PostGIS Installation
- Postgresql – Why does PostGIS create an ugly table in the database called “spatial_ref_sys”
Best Answer
A schema is like a namespace in programming. It lets you have different things with the same name.
For example, you might have a function foo() in your public schema. If PostGIS has a function foo() as well, that wouldn't work without name qualification.