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
{{ message }}
This repository has been archived by the owner on Jul 3, 2023. It is now read-only.
We are seeing a corruption issue when trying to connect to Prestogres on port 5439 using a native connector (such as pgadmin, or Spotfire Postgres). Whenever a native connector is used, Prestogres seems to get corrupted. The result is that none of the migration functions are then available. The fix to this is to recreate the data directory (prestogres-ctl create pgdata) and the re-run the migration ( prestogres-ctl migrate). Is there any way to avoid this from happening or is it possible to fix this easily?
Thanks
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We are seeing a corruption issue when trying to connect to Prestogres on port 5439 using a native connector (such as pgadmin, or Spotfire Postgres). Whenever a native connector is used, Prestogres seems to get corrupted. The result is that none of the migration functions are then available. The fix to this is to recreate the data directory (prestogres-ctl create pgdata) and the re-run the migration ( prestogres-ctl migrate). Is there any way to avoid this from happening or is it possible to fix this easily?
Thanks
The text was updated successfully, but these errors were encountered: