You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As asked in #1229, postgres 9.6 had different schema discovery structure, and yet we do not tell users that their postgresql db is too old and there might be an issue.
What we need is:
Query Postgres version (similar to how we currently detect Postgis version)
There are two ways: select version() good for printing as part of the [info] text, and SHOW server_version (or SELECT current_setting('server_version') ?) for a semver variant that can be used for testing.
Report postgres version string to the user
If postgres version is older than whichever version we currently support (some global const), give a warning, and note that that postgres is no longer maintained
The text was updated successfully, but these errors were encountered:
As asked in #1229, postgres 9.6 had different schema discovery structure, and yet we do not tell users that their postgresql db is too old and there might be an issue.
What we need is:
select version()
good for printing as part of the[info]
text, andSHOW server_version
(orSELECT current_setting('server_version')
?) for a semver variant that can be used for testing.The text was updated successfully, but these errors were encountered: