-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
jobs: change SHOW JOBS timestamps to timestamptz #108353
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, do we call this out as a breaking change? Also if we can run ./dev build
and make sure the jobs page is fine with this change?
Yesterday @rafiss said these do not need to be labeled as breaking changes: |
Release note: none. Epic: CRDB-24406.
This was a good shout. The jobs page was not fine, since some code in server/admin.go was only handing *DTimestamp. I've added a commit and ensured it is now fine. |
TFTR! bors r+ |
Build failed (retrying...): |
Build failed (retrying...): |
Build failed (retrying...): |
Build failed (retrying...): |
There appear to be some legitimate failures on this PR. bors r- |
Canceled. |
Release note (sql change): SHOW JOBS now returns times (created, last_run, etc) using the TimestampTZ column type instead of the Timestamp type, meaning they are now rendered using the session offset. Epic: CRDB-24406.
Whoops, sorry @yuzefovich! I'd scanned the red PR CIs and saw two failures (ttl job, then sql/copy) which I knew were unrelated, but missed the logic test that needed to be updated. Thanks the heads up. fixed now. bors r+ |
Build succeeded: |
Release note (sql change): SHOW JOBS now returns times (created, last_run, etc) using the TimestampTZ column type instead of the Timestamp type, meaning they are now rendered using the session offset.
Epic: CRDB-24406.