Skip to main content
Solved

PostgreSQL connection: Unknown type with OID xxx


jfd553
I am writing features in a PostgreSQL database. Everything seems OK except for the following warning...

 

 

INFORM|Truncating existing table 'public.user_locations'...

 

INFORM|Appending to existing table 'public.user_locations'...

 

WARN  |PostgreSQL connection: Unknown type with OID 24635, treating as char(-1)

 

 

What does that warning means and what should I do to get rid of it?

 

 

Since I am about to load hundreds of GB of data, I just want to be sure everything will run smoothly after the upload...

 

 

Best answer by david_r

Hi,

 

 

as far as I can tell, FME doesn's support PostgreSQL enum types. If you do not have to write to this field, you can probably safely ignore the warning.

 

 

If not you will probably have to experiment a bit to see if it is possible to work around it.

 

 

David
View original
Did this help you find an answer to your question?
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

david_r
Celebrity
  • October 9, 2014
Hi,

 

 

could it be that table public.user_locations has a field with a data type that FME doesn't know how to handle?

 

 

Consider posting the table DDL statement here (copy/paste from pgAdmin).

 

 

David

jfd553
  • Author
  • October 9, 2014
That is right, I am using an ENUM data type ...

 

CREATE TABLE user_locations (..., location_type location_enum NOT NULL, geom geography);

 

 

Can I made FME aware of this data type or should I set the field as a text data type for uploading then change it as location_enum later? 

 

 

If the content the field "location_type" seems right after uploading test data, should I wonder?

 


david_r
Celebrity
  • Best Answer
  • October 9, 2014
Hi,

 

 

as far as I can tell, FME doesn's support PostgreSQL enum types. If you do not have to write to this field, you can probably safely ignore the warning.

 

 

If not you will probably have to experiment a bit to see if it is possible to work around it.

 

 

David

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