We switched our GMS db from postgres 13 to postgre...
# all-things-deployment
h
We switched our GMS db from postgres 13 to postgres 15 some days ago, and now we see warnings like
unrecognized node type: 380
in the database log. Has anyone seen this before?
🔍 1
1
📖 1
l
Hey there 👋 I'm The DataHub Community Support bot. I'm here to help make sure the community can best support you with your request. Let's double check a few things first: ✅ There's a lot of good information on our docs site: www.datahubproject.io/docs, Have you searched there for a solution? ✅ It's not uncommon that someone has run into your exact problem before in the community. Have you searched Slack for similar issues? Did you find a solution to your issue? ❌ Sorry you weren't able to find a solution. I'm sending you some tips on info you can provide to help the community troubleshoot. Whenever you feel your issue is solved, please react ✅ to your original message to let us know!
h
We asked AWS and they responded:
Copy code
I would like to let you know that I have searched internally for the above message and have found that the message is generated when setting transaction isolation level that would result in "WARNING/ERRORS: messages on the version 14.6.

Our Internal PostgreSQL team is aware of this and currently working towards a fix, at this time these warnings can be safely ignored. It will not restrict any functionality or cause performance issues on the database.
Our DBAs say all should be fine!