So our team currently has two databases in two "independent" parts of the process. It's organizationally independent but for the actual work we do they depend on one another's output.
I wanted to make our Postgres databases into PostGIS databases. Currently the database holds some metadata and a reference to the corresponding file location on disk. To run an intersection, I'd go into the database for the file locations, run the intersection on the actual files which for our purpose isn't a big process, however, it would be more convenient if I didn't have to do that. If I could just run the intersection with a PostGIS query on a column.
From my understanding PostGIS just adds some optional things. It doesn't change any of the functionality of the database unless we use those options.
Is it a big deal then to just make a database into a PostGIS database?
Also, from my understanding, PostGIS depends on GDAL. If I currently have GDAL on my environment, could that potentially cascade down dependency conflicts with interrelated packages or is the PostGIS GDAL on the DB server and thus completely separate from my environment's GDAL?