g_spoint3_fetch wasn't "too experimental" before 1.1.5 #82
Comments
|
(I did test upgrading when submitting #74, but had picked 1.1.5 as a starting point...) |
df7cb
added a commit
to cybertec-postgresql/pgsphere
that referenced
this issue
Oct 16, 2023
…ions Allow upgrading of older installations (made pre 1.1.5) that already have g_spoint3_fetch in the spoint3 opclass. Close postgrespro#82.
df7cb
added a commit
to cybertec-postgresql/pgsphere
that referenced
this issue
Oct 18, 2023
…ions Allow upgrading of older installations (made pre 1.1.5) that already have g_spoint3_fetch in the spoint3 opclass. Close postgrespro#82.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As just mentioned in #75, there is a problem with the spoint3 change from #74:
In version 1.0, the opclass already contained the function
g_spoint3_fetchthat #74 is adding to 1.3.2.The function was declared "too experimental and preliminary" in bdc37d1 which is a mega-commit that labelled "pgsphere_1.1.4.916", so later installs don't contain it, but older installations upgraded since then will already have it.
Do we care? The fix would likely be wrapping the "alter operator family" call in upgrade_scripts/pg_sphere--1.3.1--1.3.2.sql.in into a DO block that would ignore the error when the function is already present.
The text was updated successfully, but these errors were encountered: