ThingWorx and PostgreSQL (version 15.10) Features

[Alex_Usatai]

Good morning everyone,

Sorry to bother you, but I have some questions regarding some features and functions that Thingworx Composer and PostgreSQL may use together. The context is that we are going to update our Google Cloud environment, which hosts Thingworx Composer 9.5.2 with the new version 15.10 of PostgreSQL. We are going from version 12.14 to 15.10, and my IT supervisor asked me if some of these new features and enhancements in version 15.10, are used by Thingworx. However, I was unable to answer him about those topics. Are they safe, is this something to watch out for when using some functions of the thingworx, does thingworx use some or all of them, or is there nothing to worry about? 

And I was trying to research these topics and only found about the Foreign Key in the Thingworx Help Center. Down below are the topics I mentioned, and the site from the version 15 release. If you have the time, of course, I humbly ask for your assistence and opinion, please.

The source is from the PostgreSQL site: https://www.postgresql.org/docs/15/release-15.html

1.--> Generate an error if array_to_tsvector() is passed an empty-string array element (Jean-Christophe Arnu) §

- This is prohibited because lexemes should never be empty. Users of previous Postgres releases should verify that no empty lexemes are stored because they can lead to dump/restore failures and inconsistent results.

2.--> Allow foreign key ON DELETE SET actions to affect only specified columns (Paul Martinez) §

- Previously, all of the columns in the foreign key were always affected.

3.--> Make psql include intra-query double-hyphen comments in queries sent to the server (Tom Lane, Greg Nancarrow) § §

- Previously such comments were removed from the query before being sent. Double-hyphen comments that are before any query text are not sent, and are not recorded as separate psql history entries.

4.--> Adjust psql so that Readline's meta-# command will insert a double-hyphen comment marker (Tom Lane) §

- Previously a pound marker was inserted, unless the user had taken the trouble to configure a non-default comment marker.

5.--> Make psql output all results when multiple queries are passed to the server at once (Fabien Coelho) §

- Previously, only the last query result was displayed. The old behavior can be restored by setting the SHOW_ALL_RESULTS psql variable to off. 

6.--> After an error is detected in --single-transaction mode, change the final COMMIT command to ROLLBACK only if ON_ERROR_STOP is set (Michael Paquier) §

- Previously, detection of an error in a -c command or -f script file would lead to issuing ROLLBACK at the end, regardless of the value of ON_ERROR_STOP.

Thank you very much in advance.

Have a great day.

Alex Usatai.

[Rocko · Accepted solution]

Not sure what's the goal here.

Postgres 15.10 is a supported version for your version on ThingWorx. As such it will work with that database and you can rely on that.

Which postgres features it uses and which not are product internals that should not be of interest for you, also this can change at any time with every patch release.

If you must know, this would have to be answered by product management via a support ticket, but I doubt they will give out that information.

[Alex_Usatai]

Thank you very much Mr. Rocko for the response,

We were trying to be cautious about the update, by covering all the possible errors that might come up when updating the PostgreSQL in our Cloud environment.

And you were right, we did manage to update all our environments with no problems or errors whatsoever.

And, sorry about the long time to respond to your post.

Kind Regards,

Alex

[slangley]

Hi @au_11038188 

If you are satisfied with the response you received, please mark it as the Accepted Solution for the benefit of other community members.

Regards.

--Sharon