Could you share the custom sql that is used in this connection? I am pretty sure this is what is causing the issue but I am unable to see the sql used.
1 of 1 people found this helpful
I found the issue and it was with the to_char function in postgres that was causing the issue when switching to live.
As sometimes functions used in sql work in extract but might cause issues in background.