Photo Supreme

I finally was able to update PostgreSQL to v 12. After restoring the databases, the Timeline counts returned (and expanding the years works). Maybe it was corruption in the db? No idea, but it stopped working no more than a month ago, and there were no other odd behaviors. Is there an updated versio...

Installing newest version and selecting PostgreSQL 12 (to install client libraries) did not work.

Is there a guide anywhere to upgrading the server AND how to upgrade the PS database? It's been a few years.

Thanks Hert! I am running PostgreSQL 9.6 on both Windows server and Win10 clients. It's been a few years since I set it up. I'm assuming I would need to upgrade to 12 on the server as well? I've been looking for a good reason to up to 12. Or is it only the client libraries that are the suspect here?...

I backed up the photosupreme database and put it on Dropbox. Sent a link to support@idimager.com.

Hert:

I'd be happy to. Let me know:

Format
Encoding
Dump options
Role name

The result from that script: Information ----------- 1972 1972-03 2001 2001-02 2001 2001-04 2001 2001-05 2001 2001-06 2001 2001-07 2001 2001-09 2001 2001-10 2001 2001-12 2002 2002-01 2002 2002-03 2002 2002-04 2002 2002-05 2002 2002-06 2002 2002-07 2002 2002-08 2002 2002-09 2002 2002-10 2002 2002-11 ...

Hert:

Here is the result from the script:
Information
-----------
2010
2018
2006
2003
2020
2005
2013
2009
2004
1972
2007
2012
2019
2011
2002
2001
2014
2017
2008
2015
2016


[OK]

1. Yes, after at least a month with 2-3 server reboots.
2. Screenshot attached. There are no months, only years.
3. All users are admin.
4. Using the same catalog for years, no switch.

Oddly enough, the Memories section does include a small slice of images.

PhotoSupreme on a server on PostgreSQL 9.6. Clients all at build 3044.

After one of the more recent builds, noticed all years under Timeline are zero.

How do I get the Timeline sections to update?

Hert: Thanks for this script. I was able to update the database. I had to modify the script. When I executed "drop function process_idSearchDataUpdateFTS;" I got a syntax error. I had to DROP that function manually. Then I was able to run the next two lines without errors. Connecting an updated clie...

Hert: Yes, correct PostgreSQL version always. Obviously casing is a non-issue. The script you supplied me enables me to re-create trigger and trigger function, but then the upgrade code successfully DROPS the trigger and then fails on DROPPING the trigger function . If I run the update again, I'm ri...

Hert: I ran the supplied code to create the trigger function and trigger. Upon trying to update the database via client connection I now get a new error: Unable to connect to the database. The database reports: Something went wrong while upgrading your PostgreSQL Catalog towards version 3023 (last s...

Running v5 Server Edition PostgreSQL (9.6). After updating the client and initially connecting to database, I am prompted to update the database. I then get this error: Unable to connect to the database. The database reports: Something went wrong while upgrading your PostgreSQL Catalog towards versi...

Yes I use the import module and have specific profiles as well for moving files from PC desktops to a file server (PostgreSQL version). After many versions where it was seemed less than reliable, it appears to be solid as of 5.x. Our workflow spends significant time on PCs doing ruthless culling, pr...

I purchased licenses for the upgrade to v5 PostgreSQL. Currently running v4 on a PostgreSQL 9.6 database.

What are the steps to migrate my database and upgrade the v4 clients to v5?

Should the PostgreSQL database be upgraded to v10?