Why Use a Dedicated gis Schema for PostGIS extension?
I was following this guide: Generate Vector Tiles with PostGIS.
I ran into an issue when the guide instructed me to create a new schema called gis and add PostGIS to it. However, it didn’t mention anything about setting up the necessary permissions for this schema.
From what I understand, by default, your database connection doesn’t have permission to access new schemas. I couldn’t get things to work until I moved the PostGIS extension to the extensions schema. I assume that changing the permissions on the gis schema would solve the issue, but it wasn’t clear from the guide.
This brings me to another question:
The guide says:
Why does assigning PostGIS to its own schema matter when it’s compute-heavy? Does it impact performance or resource usage in some way?
I ran into an issue when the guide instructed me to create a new schema called gis and add PostGIS to it. However, it didn’t mention anything about setting up the necessary permissions for this schema.
From what I understand, by default, your database connection doesn’t have permission to access new schemas. I couldn’t get things to work until I moved the PostGIS extension to the extensions schema. I assume that changing the permissions on the gis schema would solve the issue, but it wasn’t clear from the guide.
This brings me to another question:
The guide says:
"As PostGIS can be quite compute heavy, we recommend enabling it on a dedicated separate schema, for example, named gis!"
Why does assigning PostGIS to its own schema matter when it’s compute-heavy? Does it impact performance or resource usage in some way?
