-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
postgis2 doesn't work with PostgreSQL 11 #574
Comments
@alazarolop I think the problem is that you have installed the two versions Try only with |
I did uninstall |
@nickrobison We could rename the formula, but this could bring this problem in the others: for example #503:
@alazarolop You can close this issue Thanks for informing us about the problem. |
Thanks for reporting this! It sounds like the bottle needs to be rebuilt, which I can do now. If homebrew core has an updated version of postgis, do we need to support our own? I think the best, short term, solution is to make postgis2 keg-only and then link when we specifically need it. |
@nickrobison would postgis core formula cause incompatibilities as it uses another GDAL package and version (2.3.x) and it's updated with a slower pace? |
@nickrobison @alazarolop That's right, use p/d: I added some more things to the formula. We remember to rebuild the bottle if a new version of PostgreSQL is published. |
@alazarolop you’re correct, I hadn’t looked at the formula in a while and forgot why it was there! Glad it’s working for you and we’ll address the issues you reported. |
I have been using PostGIS extension with PostgreSQL 10 from postgis2 formula without issues, but since I've upgraded to PostgreSQL 11, postgis2 doesn't work anymore.
When I try
CREATE EXTENSION postgis ;
in a new database, I get this message:I've just installed PostgreSQL (11.1) and postgis2 (2.5.1_1) in a clean VM to test it and I get the same result. postgis (2.5.0_1) formula instead works flawlessly, which I tested by linking and unlinking both formulae, postgis and postgis2. All the rest packages from OSGeo4Mac are up to date.
The text was updated successfully, but these errors were encountered: