Skip to content
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

g_spoint3_fetch was already part of the spoint3 opclass in older vers… #83

Merged
merged 1 commit into from
Oct 18, 2023

Conversation

df7cb
Copy link
Contributor

@df7cb df7cb commented 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 #82.

…ions

Allow upgrading of older installations (made pre 1.1.5) that already
have g_spoint3_fetch in the spoint3 opclass.

Close postgrespro#82.
@vitcpp vitcpp merged commit f7ab4c4 into postgrespro:master Oct 18, 2023
15 checks passed
@df7cb df7cb deleted the spoint3-upgrade branch October 18, 2023 11:51
@esabol
Copy link
Contributor

esabol commented Oct 21, 2023

@vitcpp I propose releasing version 1.3.2.

@df7cb
Copy link
Contributor Author

df7cb commented Oct 27, 2023

Or perhaps 1.4.0?

@vitcpp
Copy link
Contributor

vitcpp commented Oct 27, 2023

Yes, 1.4.0. I think, we do it in a separate PR as a final PR before the new release. I will create an issue for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

g_spoint3_fetch wasn't "too experimental" before 1.1.5
3 participants