Postgresql 18

9 views
Skip to first unread message

Ben Wagner

unread,
Feb 6, 2026, 10:27:30 AM (5 days ago) Feb 6
to xnat_discussion
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

unread,
Feb 6, 2026, 1:08:24 PM (5 days ago) Feb 6
to xnat_di...@googlegroups.com
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

unread,
Feb 6, 2026, 1:23:21 PM (5 days ago) Feb 6
to xnat_di...@googlegroups.com
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




Ben Wagner

unread,
Feb 6, 2026, 2:33:14 PM (5 days ago) Feb 6
to xnat_di...@googlegroups.com
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

Reply all
Reply to author
Forward
0 new messages