Skip to main content
Solved

PostgreSQL 12 reading error


tsaryniuk
Contributor
Forum|alt.badge.img+1

Hi all,

There is a issue connecting to Postgresql 12.

Error executing SQL command ('SELECT c.relhasoids AS oids FROM pg_class c INNER JOIN pg_namespace n ON n.oid = c.relnamespace WHERE ...... 
'ERROR:  column c.relhasoids does not exist

According to PostgreSQL 12 documentation, the "relhasoids" column has been removed from release 12.

The error appears on both readers(PostgreSQL\PostGIS) and on different versions of FME Desktop: 18.1; 19.1; 20_beta.

At the same time, the SQLCreator transformer reads the database without any problems.

Has anyone else tested how FME works with new PostgreSQL 12?

 

Best answer by rahulsharma

Hi @tsaryniuk​ & @hellenic1994​ 

This issue is now being fixed in FME Desktop 2019.2.3 and 2020.0, please download the latest version from here.

 

View original
Did this help you find an answer to your question?

15 replies

david_r
Evangelist
  • October 14, 2019

Sounds like an issue for Safe support, it might be that Postgresql 12 isn't supported yet.


rahulsharma
Safer
Forum|alt.badge.img+10
  • Safer
  • October 18, 2019

Hi @tsaryniuk, Thanks for bringing it up. I am currently investigating (installing Postgres 12) and will update you if there is a compatibility issues with FME Desktop 2019


erik_jan
Contributor
Forum|alt.badge.img+17
  • Contributor
  • October 18, 2019

I found some references in the PostGres documentation that is was a bug (May 2019) and has been resolved (August 2019).

Could it be you have a version of PostGres 12 that was developed before August 2019?


steveatsafe
Safer
Forum|alt.badge.img+12
  • Safer
  • October 18, 2019

@tsaryniuk, Thanks for sharing.  

This does look like a problem.  I tested with Postgres 12 on my Mac OS with FME 2019.2 beta.  I can add a table to the canvas, but when I run the workspace I get the error you report.  

ERROR |Error executing SQL command ('SELECT c.relhasoids AS oids FROM pg_class c INNER JOIN pg_namespace n ON n.oid = c.relnamespace WHERE (c.relname = 'myTab'AND (n.nspname = 'public')'): 'ERROR:  column c.relhasoids does not exist
LINE 1SELECT c.relhasoids AS oids FROM pg_class c INNER JOIN pg_na...

However, you may wish to try the SQLCreator to see if that can hold you over.  I can connect and read from a non-spatial table using the SQL Creator.

The SQLCreator runs OK.  I also confirmed the version of the PostgreSQL database by running the following using SQLCreator.

SELECT version() as myversion;

Returns this on MacOS

'myversion' has value 'PostgreSQL 12.0 on x86_64-apple-darwin16.7.0, compiled by Apple LLVM version 8.1.0 (clang-802.0.42), 64-bit'

We will get this investigated.  Seems like something isn't happy.


steveatsafe
Safer
Forum|alt.badge.img+12
  • Safer
  • October 18, 2019
erik_jan wrote:

I found some references in the PostGres documentation that is was a bug (May 2019) and has been resolved (August 2019).

Could it be you have a version of PostGres 12 that was developed before August 2019?

My version was : PostgreSQL 12.0 / PostGIS 3.0.0beta1 / plv8 2.3.13. Found here: https://postgresapp.com/downloads.html and is for MacOS. I think it is newer than May. But still produces the same error. Will see what @rahulsharma figures out.


steveatsafe
Safer
Forum|alt.badge.img+12
  • Safer
  • October 24, 2019
david_r wrote:

Sounds like an issue for Safe support, it might be that Postgresql 12 isn't supported yet.

A quick update: We have created an ISSUE to investigate this. Will update when we know more.

Thanks for your patience.


tsaryniuk
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • October 25, 2019

Many thanks for replies and help)


samisnunu
Contributor
Forum|alt.badge.img+10
  • Contributor
  • October 27, 2019
steveatsafe wrote:
A quick update: We have created an ISSUE to investigate this. Will update when we know more.

Thanks for your patience.

Thanks @steveatsafe for investigation..

I have the same issue with the version: PostgreSQL 12.0, compiled by Visual C++ build 1914, 64-bit


jurgenmack
Contributor
Forum|alt.badge.img+9
  • Contributor
  • November 1, 2019

Has there been a resolution to this problem yet?


Fixed in FME 2020 Beta according to the changelog : https://downloads.safe.com/fme/beta/whatsnew_2020_0.txt


steveatsafe
Safer
Forum|alt.badge.img+12
  • Safer
  • December 10, 2019

Just to clarify this is also now fixed in FME 2019.2.1 as well as FME 2020 Beta that was reported by @lmagreaultdatto. Both are available for download now.


skjalg
Contributor
Forum|alt.badge.img+5
  • Contributor
  • December 10, 2019
jurgenmack wrote:

Has there been a resolution to this problem yet?

See https://knowledge.safe.com/comments/104090/view.html

As a temporarily workaround in case you cannot upgrade yet, you can try to use SQLCreator or SQLExectuor and manually typing your SELECT queries to read data from PostgreSQL 12. This works for me in FME 2018.1, and I suspect it will also work in earlier versions too.


hellenic1994
Contributor
Forum|alt.badge.img
  • Contributor
  • January 6, 2020
steveatsafe wrote:
A quick update: We have created an ISSUE to investigate this. Will update when we know more.

Thanks for your patience.

Hi @steveatsafe! Do you know more on said issue? Currently having the same problem with the latest versions of postgres/postgis and FME Workbench(2019.2).

 

Thanks in advance.


jovitaatsafe
Safer
Forum|alt.badge.img+11
hellenic1994 wrote:

Hi @steveatsafe! Do you know more on said issue? Currently having the same problem with the latest versions of postgres/postgis and FME Workbench(2019.2).

 

Thanks in advance.

Hi @hellenic1994,

It looks like there's been an update to FME that now supports the PostgreSQL 12 database available in builds 19807 and higher. Can you confirm that your 2019.2 build is one that includes that new support? You can check your build number in Workbench by going to Help > About FME Workbench.


rahulsharma
Safer
Forum|alt.badge.img+10
  • Safer
  • Best Answer
  • January 13, 2021

Hi @tsaryniuk​ & @hellenic1994​ 

This issue is now being fixed in FME Desktop 2019.2.3 and 2020.0, please download the latest version from here.

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings