The g-2 collaboration needs a scisoft package for version >=5.0 of pqxx (slf6-x86_64-e10).
Version 4.0.1f for our OS/arch currently exists in the scisoft package database. However, it is a few years old, and we can confirm that pqxx 4.0 does not work with the newer postgres servers that we are using.
#1 Updated by Lynn Garren over 3 years ago
- Status changed from New to Feedback
- Assignee set to Lynn Garren
- Estimated time set to 8.00 h
This is interesting. I had to dig to find anything mentioning pqxx 5.0 or later. There are no tags on the new github repository. I finally found the development snapshots: http://pqxx.org/~jtv/tmp/pqxx/snapshot/
#2 Updated by Lynn Garren over 3 years ago
- Status changed from Feedback to Assigned
However, checking the github log files finds a much newer commit:
commit 23376d4c8c4f28335e7ed408f6b63d30fe954e17 Author: Jeroen Vermeulen <email@example.com> Date: Sat Dec 24 01:00:21 2016 +0100 Tagging 5.0.0 at last. Moving on to 5.0.1.
I shall contact the author.
#4 Updated by James Stapleton over 3 years ago
We are using postgresql 9.5.2 (and soon 9.5.4). These are the servers which we verified were too new for pqxx 4_0_1f to talk to.
We intend to distribute the pqxx binary via CVMFS to many client machines. These client machines will run art jobs but (generally) will not have the postgresql server installed locally. This is why we're interested in having a solution in UPS. It seems like a much better than installing the postgres server on our clients just so we can compile the right version of pqxx. (The OS's package manager probably has the postgres server, but it will be a pretty old version because we're using SLF6.)
#5 Updated by James Stapleton over 3 years ago
I should also mention that our upgrade plan for our postgres servers is still under development right now. If the issues tying pqxx versions to specific postgresql versions turn out to be particularly messy, then we might conceivably solve the problem by only ever using matching versions of postgresql and pqxx from UPS.
I don't know whether or not this would require updated postgresql server binaries on scisoft. It's difficult to tell without a clear way of associating client and server versions.
Versions numbers are addressed by the third question of the FAQ in the old website's documentation, but it isn't very clear or up to date. (There are a couple of clues in the FAQ's changelogs here and here, but it doesn't really clear things up.)
#6 Updated by Lynn Garren over 3 years ago
The ups postgres we supply is very emphatically the client only. I presume you don't actually need the server to run everywhere, just the client.
I would like a meeting with you and Adam next week to clarify everything. Please use outlook to arrange a meeting.
#10 Updated by Lynn Garren over 3 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
pqxx v5_0_1 is now available. It is built with postgresql v9_5_5. This build is with python v2_7_11, but it can also be built with python v2_7_13b.
There is a tiny distribution manifest that can be used with pullProducts to ensure you have the proper set of ups products. http://scisoft.fnal.gov/scisoft/bundles/pqxx/v5_0_1/manifest/