Please note: If you have deleted PostgreSQL files manually then your old database will probably not be recoverable unless you made the recommended Backup before starting the update.
If you uninstalled but did not manually delete any files then your old database should still exist if you re-install the same major version of PostgreSQL as you previously had.
Please follow
this guide for how to fully uninstall and re-install PostgreSQL. It refers to v9.3 but you may have had another version such as 9.6 or 12, depending on when you first installed PT4. As long as you didn't delete the whole PostgreSQL folder structure you will be able to see which version you had installed there. If you deleted everything, then I would recommend installing the latest version of PostgreSQL 12, and creating a new database with that.
Most of what follows will only apply if you are able to recover your existing PostgreSQL version and database. Otherwise you will need to create a new database once you have reinstalled PostgreSQL.
---
As far as I'm aware "some_time" is not part of the PT4 database structure. Is it possible that you made external changes to your database, maybe as part of a third party Hud install or something like that?
If so, then you may be able to re-apply the recommended changes to get it working again. However, external changes to the database are not something that we recommend or support so if that is the case then you would need to contact the supplier for further directions.
In the meantime, if you made the recommended Backup before running the database update then you could temporarily revert to
v4.17.13 and restore your Backup. However, this change is very unlikely to be reverted so the problem will remain for future updates too, so it would be better to try to resolve it now.
Alternatively, you could create a new database and re-import your hand histories.
If you did not make any external changes to your database please upload your Backup file to cloud storage (e.g. Dropbox, Google Drive, OneDrive, etc) and share the link via a
Support Ticket so that we can investigate for you.