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
Describe the bug
Try to restore a .backup file with pgAdmin 8.14, but fails with transaction_timeout failure : pgadmin-org/pgadmin4#8171
Probably due to the last upgrade : #523
To Reproduce
Exact steps to reproduce the behavior:
Go to a Pull request
Download datamodel dumps
Try restore .backup
See error
Expected behavior
Dumps are restored succesfully.
Screenshots / data
If applicable, add screenshots or data to help explain your problem.
Desktop (please complete the following information):
TWW version
QGIS Version
OS
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
If you go further in versions, you could copy and define 16.4 pg_dump / pg_restore libraries with the pgAdmin preferences section pgadmin-org/pgadmin4#7114 (comment)
ponceta
changed the title
CI PG restore is not match with current PG admin pg_restore version
Do not upgrade pgAdmin 18.12 (max) / CI PG restore is not match with current PG admin pg_restore version
Jan 13, 2025
I encountered the same problem while transferring the data form one DB to another. Both source and target DB were using v16 and PgAdmin was using v17. I solved this problem by downloading the PgAdmin v16 to and it solved my problem . You can download from here
Describe the bug
Try to restore a .backup file with pgAdmin 8.14, but fails with transaction_timeout failure :
pgadmin-org/pgadmin4#8171
Probably due to the last upgrade :
#523
To Reproduce
Exact steps to reproduce the behavior:
Expected behavior
Dumps are restored succesfully.
Screenshots / data
If applicable, add screenshots or data to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: