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

Feature Request: check version mismatch #735

Open
jw1u1 opened this issue Jan 22, 2025 · 3 comments
Open

Feature Request: check version mismatch #735

jw1u1 opened this issue Jan 22, 2025 · 3 comments

Comments

@jw1u1
Copy link

jw1u1 commented Jan 22, 2025

Hi Keith,

some partman functions like run_maintenance silently do nothing, if the loaded shared_preload_library is a newer version than the currently installed version in the database.
I would be helpful to have clear error messages in this case.

Rgds, Jens

@jw1u1 jw1u1 closed this as completed Jan 23, 2025
@keithf4
Copy link
Collaborator

keithf4 commented Jan 23, 2025

Just to clarify, was there an issue with the library version mismatch? I'd responded to the other issue that it may have been that there was no new data that was causing nothing to happen. Was that the case for you as well?

@jw1u1
Copy link
Author

jw1u1 commented Jan 23, 2025

We have infinite_time_partition set to true and after restarting postgres it worked as expected, so i guess it has nothing to do with no new data.

@keithf4
Copy link
Collaborator

keithf4 commented Jan 23, 2025

Going to re-open this one to investigate in the future.
Not sure I can get the plpgsql function to throw a mismatch error, but I think I can get the library to throw and error in the logs if there's not a minimum version of the extension installed in the database

@keithf4 keithf4 reopened this Jan 23, 2025
@keithf4 keithf4 added this to the Future milestone Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants