Posgresql 9.6.1 Bug
Good Day
Please see below the error that we getting after upgrading our PostgreSQL to 9.6.1 from 9.4. Please advise if we need a latest patch for the bug.
We are getting the following when starting up JBoss with Postgres 9.6.1:
"ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ServerService Thread Pool -- 62) ERROR: column am.amcanorder does not exist"
Regards;
Lucky Maphumulo
0877368417.
To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser:
https://www.fnb.co.za/about-fnb/legal-matters/email-disclaimer.html
If you are unable to access the Disclaimer, send a blank e-mail to
firstrandbankdisclaimer@fnb.co.za and we will send you a copy of the Disclaimer.
On Mon, Feb 20, 2017 at 12:56 AM, Maphumulo, Ncebo <nmaphumulo@fnb.co.za>
wrote:
Good Day
Please see below the error that we getting after upgrading our PostgreSQL
to 9.6.1 from 9.4. Please advise if we need a latest patch for the bug.We are getting the following when starting up JBoss with Postgres 9.6.1:
Not our bug though we did change this behavior/structure in 9.6:
From the docs:
https://www.postgresql.org/docs/9.6/static/catalog-pg-am.html
"""
Note: Before PostgreSQL 9.6, pg_am contained many additional columns
representing properties of index access methods. That data is now only
directly visible at the C code level. However,
pg_index_column_has_property() and related functions have been added to
allow SQL queries to inspect index access method properties; see Table 9-62.
"""
I'm supposing the structure of pg_catalog objects are deemed implementation
details is why they lack of a release note compatibility item - though it
does show up in 3.3.12 of the 9.6.0 notes.
David J.
"Maphumulo, Ncebo" <nmaphumulo@fnb.co.za> writes:
We are getting the following when starting up JBoss with Postgres 9.6.1:
"ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ServerService Thread Pool -- 62) ERROR: column am.amcanorder does not exist"
That is not a Postgres bug. It indicates that something on the client
side has not been updated for the system catalog changes that were made
in PG 9.6. You probably need to talk to the JBoss folk about whether
they support 9.6 yet.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 21/02/17 04:44, Tom Lane wrote:
"Maphumulo, Ncebo" <nmaphumulo@fnb.co.za> writes:
We are getting the following when starting up JBoss with Postgres 9.6.1:
"ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ServerService Thread Pool -- 62) ERROR: column am.amcanorder does not exist"That is not a Postgres bug. It indicates that something on the client
side has not been updated for the system catalog changes that were made
in PG 9.6. You probably need to talk to the JBoss folk about whether
they support 9.6 yet.
Probably need a later jdbc driver jar at least (looking at the postgres
jdbc web site it is not immediately obvious what version you need for
9.6 support, grovelling through the release notes suggests from 9.4.1209
upto latest version 42 should do it).
regards
Mark
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs