V6 Update database update; how long?

[paulrbarnard]

I've upgraded to V6 about 11 minutes ago. I still have the window saying "Your database is updating". Any idea how long this should take? Versions have updated databases in teh past but it has only ever taken a couple of minutes. I have about 30k images in the catalogue.

[paulrbarnard]

30 minutes and still sat there. I'm going to kill it despite the warning "It may cause permanent damage to your database"

[paulrbarnard]

Relaunched after forced quit and it said an update is already in progress. Selected to continue anyway and I'm now running.

[paulrbarnard]

A word of caution is needed I think.

I just updated my laptop and it experienced the stuck at updating the database point as well. This went worse as after about 5 minutes the entire laptop crashed and restarted. Like my main computer on the second attempt it completed fine.

It's very odd that it failed on both my computers. They are using different catalogs, not do any fancy sharing or anything like that. Bother were running the latest V5 release to the best of my knowledge.

[G8DHE]

Just done similar on main Workstation and then Laptop no problems with the conversion but having real problems when a Drop-down list appears to make a selection from various errors appear ....

[Frankyls]

I have the latest iMac with 40 GB memory - upgrading the DB is now since 40 min running - REALLY !?

[Frankyls]

The database upgrade from the latest V5 to the latest V6 version is fairly small and should not take longer than 5 minutes (more like 5 seconds). If you come from an early V5 version or even an older PSU main version then upgrading can take a while to complete.

No, it is the latest V5 version.

[Hert]

The database upgrade from the latest V5 to the latest V6 version is fairly small and should not take longer than 5 minutes (more like 5 seconds). If you come from an early V5 version or even an older PSU main version then upgrading can take a while to complete.

[OldRadioGuy]

Installed V6, started and elected to update the v5 database. Went to breakfast with the progress window displayed. Returned after breakfast, and the progress window showed no progress. Performed an iMac Force Quit twice to shut down V6. Restarted V6 and the progress window returned, showing completed task. It quickly disappeared and V6 then started up normally.

My initial reaction ... V6 is much faster, more responsive. But I have not yet experimented with the nasty Google Maps - GPS function.

My system:

macOS Big Sur version 11.2.1
iMac (Retina 5K, 27-inch, 2017)
Processor 4.2 GHz Quad-Core Intel Core i7
Memory 32 GB 2400 MHz DDR4
Graphics Radeon Pro 580 8 GB

[Frankyls]

I uninstalled this new V6 thing - really unhappy - maybe it is working better in several week.

[Username]

I suffered the same problem.

Backup V5 postgres db
Installed V6
Ran, choose update and got stuck in a loop of nothing.
Sat it out for 10 minutes and forced quit.
Ran the V6 server från the server itself and updated the DB without a problem.
Quit the server app locally on the server.
Launched Server app on client and got the "another process" dialog.
Sat it out for 30 min but nothing.
Forced quit and launched again and connected perfectly.

Received the update notice for 3540 and installed it.
Launched it and all works fine again.

Did a new db backup or v6.

[Al_M]

I am on my third try. (macOS Big Sur -11.1, PostgreSQL 12)
So far each time I elect to upgrade and I get the spinning beach ball. The first 2 times I force quit after about 20 minutes each.
The third time I am letting it go longer....so far 30 minutes.
I was running a very recent build of PhotoSupreme 5 Server (build 3432).
I uninstalled V5 by dragging to the trash bin, then installed V6.
Ran macOS Activity Monitor, postgre is using 1.29 GB of memory. PhotoSupreme 149.8 MB and "not responding".
Under CPU, PSu is showing 0% and postgre using 8 threads all at 0%.
I really looks like nothing is happening in the background.
How long should I let it go and what next??
Really frustrating.

[Hert]

If you come from build 3432 then the database upgrade shouldn't take too long, depending on the number of image you have in the catalog that have areas defined for them. If there are many images with many areas then please give it time to complete.

Background info: In V6, PSU indexes more details from the areas. If you have a large number of images with areas then that step may take a while to complete. During that step there is no visual feedback and so you'll get the beach ball on macOS or hourglass in Windows. When in doubt, check your CPU usage, it's probably still working and will eventually finish.

PS. If you kill during that step and then restart PSU then the area indexing will restart from the beginning, so please don't kill it.

[Al_M]

Hert,
Thanks for the quick response!
Out of 45,000+ images around 600 of them use areas.
It's been over an hour now, and still at the "Do you want to upgrade the database?" info dialog and spinning beach ball...
CPU Usage is 0% for PhotoSupreme and 0% for 8 threads of PosgreSQL.
I really cannot tell if there is something happening or not.
Is there any other method for determining if there is actual activity or just locked up?

[Hert]

If cpu usage is 0 for a longer period then kill it. After restart you’ll get a message that an upgrade is running. Click the button at the bottom to ignore that and continue