You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ok, did some testing with this on staging postgres — couldn't find a syntax that worked for specifying the timezone, but then I had a thought and tried the pgloader without setting the timezone at all, and it looks to me like the dates came through properly. (The thought that occurred to me: maybe setting the timezone the way we did was what caused the discrepancy.)
It looks to me like we don't need to do anything to get the dates to come through properly, but we should confirm when we test — maybe when we run the migration in production.
Confirmed when we ran pgloader on the new production system: omitting the timezone resulted in the correct behavior — log entries in the new production database and old production database have the same time.
No description provided.
The text was updated successfully, but these errors were encountered: