Postgresql 18

[Ben Wagner]

Hi XNAT,

  What is the status of XNAT with Postgresql 18?  I'm planning on moving our XNAT database from 12 (EOL 2024) to something newer and I'm hoping to go to something that will last for a while.

Also, I need an update to the previous thread on "Broken datatype displays."  Please!

Ben

[Rick Herrick]

I have not tried XNAT on PostgreSQL 18 yet. I actually may have found a minor incompatibility with PostgreSQL 17, but haven't had a chance to look into it in detail yet due to on-going XNAT 1.10.0 release work and client needs.

We'll try to get back to you soon on the broken datatype displays issue. See "on-going XNAT 1.10.0 release work and client needs" again :)

Rick Herrick 

Senior Software Developer

ri...@xnatworks.io

https://xnatworks.io | Find us on LinkedIn! 

--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xnat_discussi...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/xnat_discussion/CADVL1QzGp%2B7hJDj3AQeCcX7NcN44dQ_yr03JxT9jVVmH%3Dq0%3Dpw%40mail.gmail.com.

[Timothy Olsen]

To confirm what Rick said.  I think Postgresql 16 is our latest tested version we can commit to at present.

For the broken listing, the bottleneck has been setting up an environment to reproduce it.  If you have an environment where it is happening, it would be a lot quicker if we could just hop on a call and look at that.  Feel free to grab some time here:
https://calendly.com/timothyolsen/

Tim

Timothy R Olsen 

Founder, President

 t...@xnatworks.io

 xnatworks.io | Find us on LinkedIn! 

To view this discussion visit https://groups.google.com/d/msgid/xnat_discussion/CAFykhbB_ZgT6ti0CmPzSgX62wqQ%3D8hHM-NEDbeugnLWyUk_yew%40mail.gmail.com.

[Ben Wagner]

Thanks Tim and Rick,

  16 EOL's in 2028..so is a possible upgrade route.  It's just such a massive pain to do.  Is the possible 17 incompatibility a minor point release fix or a more serious issue?  I.E, something that will probably come out with or before 1.10 or after?  I'm just trying to gauge if I should wait a few weeks for 17 or just go with 16.

  Tim, I've scheduled some time on Tuesday.  Thanks!

Ben

To view this discussion visit https://groups.google.com/d/msgid/xnat_discussion/CAOAXJbZ%3DOFX7aBrB0-g-sTejiUVYopCz%3DPd0hgsMQnDzRqwpww%40mail.gmail.com.

[Schnei Gamu]

Hi all,

Could you give us an update on the PostgreSQL 17  incompatibility? We also need to upgrade, and would like to go to PostgreSQL 17 if possible. 

Best,

Nils

[Timothy Olsen]

This won't be in XNAT 1.10.  But, we will hopefully get to it in the following release.

If you are looking to upgrade in the next month or 2, I would go with Postgesql 16.  

Tim

Timothy R Olsen 

Founder, President

 t...@xnatworks.io

 xnatworks.io | Find us on LinkedIn! 

To view this discussion visit https://groups.google.com/d/msgid/xnat_discussion/a4603fb0-7b1a-4f84-a9cc-303f29639f04n%40googlegroups.com.

[Schnei Gamu]

Hi Tim, Rick,

Thanks for the update, unfortunately our IT department is insisting on Postgresql 17 if we cannot show an obvious problem with Xnat. Could you tell us some more information what the incompatibility entails? 

Thanks,

Nils

[Rick Herrick]

Hey Nils,

Just FYI, I recently ran our full battery of REST tests against XNAT 1.10.1-SNAPSHOT (our latest development code) deployed on PostgreSQL 16, 17, and 18. The results of all three test suites were consistent: each had only a few errors, all located in the same area of code, with nothing indicating issues with incompatibility with particular database versions. I believe the errors that I saw previously that I thought were caused by issues with PostgreSQL 17 were actually caused by another issue that coincidentally occurred when I first tried running on that version!

Rick Herrick 

Senior Software Developer

ri...@xnatworks.io

https://xnatworks.io | Find us on LinkedIn! 

To view this discussion visit https://groups.google.com/d/msgid/xnat_discussion/e885871a-bc96-484b-9a24-e8d8e6c70934n%40googlegroups.com.

[Schnei Gamu]

Hi Rick,

That is great news, thanks for testing! We tested PostgreSQL 17 on our dev system and also did not find any problems. 

Best,

Nils

[Rick Herrick]

Thanks for the info! If you find anything that does look like it relates to database incompatibility please let us know, but from what we've seen in our testing 17 and 18 both appear pretty solid.

Rick Herrick 

Senior Software Developer

ri...@xnatworks.io

https://xnatworks.io | Find us on LinkedIn! 

To view this discussion visit https://groups.google.com/d/msgid/xnat_discussion/e719479f-d821-49ce-9325-610401bf5259n%40googlegroups.com.