Supported PostgreSQL Versions

 

This page is designed to keep users informed about the PostgreSQL versions currently supported by xTuple.

xTuple version

PostgreSQL version

1.x

7.6 - 8.1

2.x

8.1 - 8.2

3.0.x-3.2.x

8.1 - 8.3

3.3.x

8.2 - 8.3

3.4.x+

8.2 - 8.4

xTuple ERP versions prior to 3.0 are not supported on PostgreSQL 8.3.x. If you are running xTuple 2.3.2 or older, you should not be running on PostgreSQL 8.3 or newer.

ALSO NOTE: Users who load backup files (e.g., empty.backup, quickstart.backup, and demo.backup) should be advised that as of xTuple 3.2.2 those backup files are being dumped from a PostgreSQL 8.3 database. That means the backups must also be loaded on PostgreSQL 8.3 (or higher) to avoid backward incompatibility problems.

Wed, 02/02/2011 - 22:22
#1
jetaf
jetaf's picture
Offline
Joined: 01/24/2011
Incongruous Incompatibility

There is something wrong in your compatibility table

I am using PostgreSQL v 8.4
with
PostBooks ERP v 3.6.0

and get

"The version of the database you are connecting to is not the version this client was designed to work against. This client was designed to work against the database version 3.6.0. The system has been configured to disallow access in this case.
Please contact your systems administrator.

It does however work with PostBooks ERP v 3.6.1"

Top
Wed, 02/02/2011 - 23:15
#2
ned
ned's picture
Online
Joined: 10/20/2008
That error message refers to

That error message refers to the xTuple client and the xTuple database matching version numbers (3.6.x). It doesn't have anything to do with PostgreSQL version number.

Top
Thu, 02/03/2011 - 00:25
#3
jetaf
jetaf's picture
Offline
Joined: 01/24/2011
Yes, I see that now

There is no 3.6.1 PostBooks-installer, currently the highest is only 3.6.0. Therefore when you do a full install that client, though it works locally, will not connect to a remote database restored from the 3.6.1 database tables. There is, of course, a version miss-match. I suggest this may be initially confusing, as it was to me, because you tend to assume the latest would work remotely as it does on its own local installation. You might like to put a note on your Supported Postgres Versions page to highlight for people who like me see the version incompatibility error message and end up at that table trying to identify what the incompatibility is.

There is of course a client only GUI 3.6.1 available which solved the problem for me.

Top