Photo Supreme

For the benefit of anyone reading here but not checking release notes, I noted that the PostgreSQL memory utilization improvements in version 2023.2.0.5063 appear to include universal deallocation of prepared statements (very nice).

Syncing/writing to about 6,600 files stayed within 1 GB of the ...

I had reason to be looking at SQL activity related to a separate issue but I think I noted what is the key issue with Photo Supreme and PostgreSQL specifically.
Note that you don't have to do anything intensive to exhaust memory, you just have to do enough in a single session. If you do something so ...

Synchronization Settings->XMP Storage Location set to 'Always as a sidecar file' presumably accomplishes what you want. It isn't file type specific, but you could change the option and manually save to other types if you wanted to write into other file types and not just universally to XMP sidecar ...

I should note that I will do a bug report on both issues, but unlike the Similar Image list issue (which is clearly a bug) I wasn't certain the failure to update from manual changes to version sets impacted everyone, but with that confirmed, I'll go the bug report route for that too. Thanks for the ...

I was trying to keep the topic focused on the list updating to accurately reflect version set changes because it is easy to describe. When just refreshing the list resolved it I didn't bring it up for that scenario because the bar was low. As I noted in the original post, I'm fully aware that ...

As far as I know this issue doesn't have a long-term impact but if you are doing a lot of manual version set changes it becomes quite a nuisance because you have to repeatedly reload whatever list you are working with to get an accurate display. You are left unable to access certain items without ...

Unless you have a massive catalog I wouldn't expect those settings to be a problem in terms of being too low.

Regardless of how it is triggered, the operation hitting some bottleneck related to disk IO is still the likely suspect for any system, but it is especially so since you are running in a ...

From experience I can say system specs certainly should be capable of running a perfectly functional PostgreSQL instance if properly configured (I'm doing fine with 32GB RAM, 2 CPUs/8 cores total for PostgreSQL hosting and network file share hosting but running directly on the physical Linux system ...

I use PostgreSQL on a dedicated Linux system to host Photo Supreme.
I have over 340,000 items in my catalog and I certainly don't have any operation I've encountered that takes 10-15 minutes.

If you can describe something specific that is causing a 10-15 minute delay I can test and see what ...

I saw this is addressed in build 4494, so for anyone reading this in the future:
"Build 4494; When searching using the Search Box then the "full data value" is now also searched (not only the search tokens generated from a search value) ; e.g. IMG_1337 will give a result now"

Thanks!

That can get you the specific item in this example but is still less useful (points 1 and 2 below) than if the full reference was a separate term and isn't a practical/viable substitute (point 3) for a specific term including the full exact characters of the reference/filename.
1. You have to know ...

It occurred to me after making the first post that the missing content might be separately searchable, and sure enough, it is, so you can separately find the portions of the reference (along with any other items that they overlap with) but cannot find the specific combined reference.
E.g. item with ...

Maybe this is just something that happened to me as a result of some circumstance, but the recent update that changed the structure of search data seems to have truncated the search values at e.g. spaces, underscores, hyphens, etc.

E.g. there are 54 items in the catalog with names that begin with ...

I had this exact issue with a small number of files for some number of months in 2021. Like you I usually am using the Custom Thumbnail Info view and have some label rows that were comprised of multiple macro values.
I recorded diagnostic data back in November 2021 and got to the point of noting ...

I just wanted to add a quick note to this topic with a visual to back it up to make the point for anyone that has a folder turn red due to having been moved, or a drive having disconnected, etc. Whatever you do, don't go the route of removing the now red folder from the catalog if you want any ...