Is it safe to forcefully shut down reindexing?

[Detrusitol]

Hello!

I changed computers and after restoring the first backup, the database practically didn't work at all. I received notifications to perform database maintenance tasks, but they did absolutely nothing.

I performed the same maintenance tasks on the old computer, and each task only took a few hours, even though it is an old laptop

After that, I took several backups and noticed that if I selected 'Processed hands,' only those Processed Hands were available in the restoring files options when restoring the database. So, I took another backup without 'Processed hands' and restored it to the new computer.

Now I thought I would perform the database maintenance tasks once more on this new computer, but reindexing has already taken a long time, and according to Task Manager, nothing seems to be happening.

Why does the same database work flawlessly on the old computer, but has such significant difficulties functioning correctly on this new one? Is it possible that something unusual happens during the backup and restore process?

Thanks in advance :geek:

Näyttökuva 2024-07-01 022704.png

(28.9 KiB) Downloaded 1293 times

[Flag_Hippo]

After that, I took several backups and noticed that if I selected 'Processed hands,' only those Processed Hands were available in the restoring files options when restoring the database.

Processed hands are the original hand history files from your poker site(s) that PokerTracker 4 has archived and they do not form a part of the actual database:

Guide: Processed Files

Now I thought I would perform the database maintenance tasks once more on this new computer, but reindexing has already taken a long time, and according to Task Manager, nothing seems to be happening.

If things are taking much longer on the new computer and there is no PostgreSQL activity in Task Manager then I would cancel the housekeeping and not use that database. In the meantime you can create a new database and import from your original hand history files using 'Play Poker -> Get Hands From Disk'.

Why does the same database work flawlessly on the old computer, but has such significant difficulties functioning correctly on this new one? Is it possible that something unusual happens during the backup and restore process?

I don't know what would be causing that and a database should be restored in much the same state it was when it was backed up but if you open a Support Ticket we can follow up on this with you. If you can share the backup file using cloud storage then please provide a link in the ticket but if not we can give you details of how to share it with us. Also please include a link to this thread in your ticket and let us know what version of PokerTracker 4 was used for the backup, what version of PokerTracker 4 is being used for the restore and which versions of PostgreSQL are running on each computer.

[Detrusitol]

If things are taking much longer on the new computer and there is no PostgreSQL activity in Task Manager then I would cancel the housekeeping and not use that database. In the meantime you can create a new database

Interesting that the instructions you linked for creating a new database seem to completely resolve the issue. I didn't do anything other than select that a new database already exists and choose that existing one. So basically just a new name for the database. After this, all maintenance operations were completed within an hour, and the import seems to be working smoothly.

I'll keep ticket #T1063649 open in case the technician can find something that is causing the problem and those weird situations with backing up and restoring

Thanks for the help :)