acertain wrote: 15 Apr 21 17:47
I just created a new catalog. And then tried to exit PSu. Instead, I got an exception.
"Field not found"???? That should not be possible and if that field is missing in your database then yes, very strange things will happen and in that case I'm not surprised that you get crashes all the time.
Maybe you can share some details about your PostgreSQL installation and about the server hardware and OS that your PostgreSQL database is running on. And important: I hope you *never* touched anything in the database structure yourself. Something is definitely wrong in your database.
You can send me a copy of your database backup as created with pgAdmin, so I can check it here.
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
Hert wrote: 04 Apr 21 21:34
You can create a PostgreSQL backup as described in the Maintenance manual.
Restoring is also explained in the Maintenance manual.
OK, but if my database is corrupted, how I using pg backup and restore going to help? I was trying to use the PSu backup and restore. Are you telling me that that doesn't actually work with the server version? If so, maybe you should get rid of those menu options.
acertain wrote: 15 Apr 21 17:47
I just created a new catalog. And then tried to exit PSu. Instead, I got an exception.
"Field not found"???? That should not be possible and if that field is missing in your database then yes, very strange things will happen and in that case I'm not surprised that you get crashes all the time.
Maybe you can share some details about your PostgreSQL installation and about the server hardware and OS that your PostgreSQL database is running on. And important: I hope you *never* touched anything in the database structure yourself. Something is definitely wrong in your database.
You can send me a copy of your database backup as created with pgAdmin, so I can check it here.
You want the brand new, empty catalog that got created? Have you tried reproing yourself? Create a brand new catalog. Open it. Create another brand new catalog. Try to close your application.
But happy to send you my pg database backup of either the empty ones or a new one. What's the best way to get it to you? I can put it in S3 if you give me an email to send you the link.
I'm running Ubuntu 20.04 with up-to-date PostreSQL 10. I have never touched anything in the database.
I deleted all versions of PSu from my machine and the registry keys. I then downloaded a new version of PSu 6. I told it to create a new database on a local Postgres server running on my windows machine (not the one I use normally for PSu). Then I told it to create another new database. Then I tried to quit. I got the missing key error. Are you really unable to repro?
Now I’m also on postgres server version although on macOS. But I thought I’ll do some testing with this as well just to see.
I run my Postgres on a macOS server via the postgres.app ( postgresapp.com )
I tested pg10, 11 and pg12 and they performed as Hert’s video shows.
But I did this on my own MacBook Pro running Big sur and initially got problem when the PSu was about to populate the db. It just halted and sat there for hours.
This was due to the postgres app did not have disk permissions for the temp location I chose for the database.
Where are your db storage located on your postgres hosts?
Any possibility it can be a permissions problem?
PSu Server 2024 & Postgres 15 on macOS 14
PSO 6 on Windows Server 2022
Sorry for the long hiatus. Work keeps intruding on life!
Here's where I am with the main issues on this thread. I think that I had two overlapping problems. The first, which was seen in the OP, was that my HDD-based database was struggling to keep up when I made lots of changes (import a bunch of images, verify a big folder, whatever). Upgrading my server to all SSDs fixed that.
The second issue, of the poof crashes, I don't know. However, the client machine had had several versions of both stand-alone and database PSu installed over time. I uninstalled everything PSu related, including the registry, and reinstalled. And I'm not getting the crashes any longer. So who knows what the root cause was, but maybe some DLL was corrupted at some point.
Overall, then, my main issues are solved. I do have a few other smaller questions, for which I will start new threads.
Thanks.
Andrew
PS. I did follow all the Postgres install instructions. I can recheck the config.