Golang Go语言中求助广大V友，golang PostgreSQL时间字段差8个时区怎么办？

没看到实际数据，但是按照 UTC 取，差 8 个时区应该就对啊，2023-09-01T15:00:00Z 就等于 2023-09-01T23:00:00+08:00

问题就在于， 我的数据库时区是 Asia/Shanghai ， 像 created_at 这种字段，使用数据库的默认值，就是当前时区的值， 然后用程序插入的字段使用的是 UTC ，就会出现 ， 刚学个毛皮，不知道怎么弄合适了

同意#3
1. 没有存量负担时，坚持用 timestamp with timezone 类型
2. 自己用客户端人肉查询处理问题时，可以先 set timezone 指定时区
3. 如果涉及到索引，可以针对业务上常用的时区做基于函数的索引，或者用触发器弄一个索引列

这不是项目跨不跨国的问题，而是 timestamp without timezone 的读写是直接吞掉时区的，指不定哪个环节配置不对或者哪个库处理不对就不可控了，用 with timezone ，跟外部交换时根据客户端的时区做转换，内部存储则用 UTC ，这是确定的

摘自 python datetime 的文档 https://docs.python.org/3/library/datetime.html

Date and time objects may be categorized as “aware” or “naive” depending on whether or not they include timezone information.

With sufficient knowledge of applicable algorithmic and political time adjustments, such as time zone and daylight saving time information, an aware object can locate itself relative to other aware objects. An aware object represents a specific moment in time that is not open to interpretation.

A naive object does not contain enough information to unambiguously locate itself relative to other date/time objects. Whether a naive object represents Coordinated Universal Time (UTC), local time, or time in some other timezone is purely up to the program, just like it is up to the program whether a particular number represents metres, miles, or mass. Naive objects are easy to understand and to work with, at the cost of ignoring some aspects of reality.

使用 timestamp with timezone 保存的就是 aware object ，不需要外部依赖就能保证信息的完整性。个人建议均使用 timestamp with timezone 。