sql: tzinfo can be inconsistent across nodes

[jseldess]

Jesse Seldess (jseldess) commented:

See cockroachdb/cockroach#31978 (comment).

CockroachDB relies on each node's tzinfo data for resolving named timezones like America/New_York and for applying daylight-savings rules. This can lead to inconsistent results across a cluster when coercing date/time strings into temporal types.

From @knz:

until this issue is fixed, we should call out in the docs for operational matters that the OS database should be updated, and all nodes should be restarted when the timezone data changes (e.g. the definition of a timezone changes because of geopolitical matters, or some country decides to change their DST rules).

Jira Issue: DOC-202

[jseldess]

We have closed this issue because it is more than 3 years
old. If this issue is still relevant, please add a comment and re-open
the issue. Thank you for your contribution to CockroachDB docs!

[rmloveland]

This issue is still open in CRDB repo, reopening

[exalate-issue-sync]

Jesse Seldess (jseldess) commented:
We made a bunch of changes to our docs for this. See cockroachdb/cockroach#31978 (comment) . I’m not sure there’s anything else for us to do right now. When the cockroach issue gets resolved, there should be a release note that would create a docs issue. Also, this isn’t really a SQL issue. It’s a deploy issue. In any case, we’ll leave it open in favor of more investigation.