Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

figure out and test pgloader timezone syntax #486

Closed
Tracked by #473
quadrismegistus opened this issue Nov 14, 2022 · 2 comments
Closed
Tracked by #473

figure out and test pgloader timezone syntax #486

quadrismegistus opened this issue Nov 14, 2022 · 2 comments
Assignees
Labels

Comments

@quadrismegistus
Copy link
Contributor

No description provided.

@rlskoeser
Copy link
Contributor

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.

@rlskoeser
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants