Which timezone offset does Talos preserve during DATE type casts?

Talos stores all timestamps as UTC epoch milliseconds, discarding any client-provided time zone information at write time. This design ensures consistent internal representation but raises questions about how timezone context is preserved during subsequent date type conversions.

Date conversion functions default to the server's configured time zone when a session-level timezone parameter is absent, which can produce unexpected results for users in regions offset from the server. The documentation does not currently clarify how Talos resolves ambiguous local times, particularly during daylight saving time transitions, when converting between DATE, TIMESTAMP, and related types.

It remains uncertain whether Talos retains the original timezone offset when performing casts such as TIMESTAMP to DATE, or whether the offset is silently dropped. Behavior may also differ across major releases, with the latest stable version (v5.2) potentially altering default timezone handling compared to earlier releases.

• Which timezone offset, if any, does Talos preserve during a TIMESTAMP to DATE type cast?
• Does the session-level timezone parameter affect how ambiguous local times are resolved during DST transition periods?
• How does Talos's timestamp handling differ between major releases when converting date types across regions?