在postgres中获取具有时区偏移量的日期(Getting date with timezone offset)

 不可以。推理参见以下FAQ： 
 
 常见问题：我可以停止对我未使用的变量/导入的投诉吗？ 
 
 
 
 未使用的变量可能表示一个错误，而未使用的导入只会减慢编译速度，随着程序逐渐累积代码和程序员，这种效应可能会变得很大。 出于这些原因，Go拒绝使用未使用的变量或导入来编译程序，交换短期便利以实现长期的编译速度和程序清晰度。 
 
 
 尽管如此，在开发代码时，通常会暂时创建这些情况，并且在程序编译之前必须将它们编辑出来可能很烦人。 
 
 
 一些人已经要求编译器选项关闭这些检查或至少将它们减少到警告。 不过，这样的选项还没有被添加，因为编译器选项不应该影响语言的语义，因为Go编译器不会报告警告，而只会报告阻止编译的错误。 
 
 
 没有警告有两个原因。 首先，如果值得投诉，值得在代码中修复。 （如果不值得修复，则不值得一提）。其次，让编译器生成警告会鼓励实现警告有关可能导致编译噪声的弱情况，从而掩盖应该修复的实际错误。 
 
 
 但是，解决这种情况很容易。 在开发过程中使用空白标识符让未使用的东西持续存在。 
 
 
 你可能要做的是在临时想要排除某些东西时使用空白标识符，例如 
 
import (
    "fmt"
    _ "time"  // This will make the compiler stop complaining
)
 
 
 
 现在，大多数Go程序员使用工具goimports ，它会自动重写Go源文件以具有正确的导入，从而在实践中消除未使用的导入问题。 这个程序很容易连接到大多数编辑器，以便在编写Go源文件时自动运行。 
 

No. For reasoning see the following FAQ:
 
FAQ: Can I stop these complaints about my unused variable/import?
 
 
 
The presence of an unused variable may indicate a bug, while unused imports just slow down compilation, an effect that can become substantial as a program accumulates code and programmers over time. For these reasons, Go refuses to compile programs with unused variables or imports, trading short-term convenience for long-term build speed and program clarity.
 
 
Still, when developing code, it's common to create these situations temporarily and it can be annoying to have to edit them out before the program will compile.
 
 
Some have asked for a compiler option to turn those checks off or at least reduce them to warnings. Such an option has not been added, though, because compiler options should not affect the semantics of the language and because the Go compiler does not report warnings, only errors that prevent compilation.
 
 
There are two reasons for having no warnings. First, if it's worth complaining about, it's worth fixing in the code. (And if it's not worth fixing, it's not worth mentioning.) Second, having the compiler generate warnings encourages the implementation to warn about weak cases that can make compilation noisy, masking real errors that should be fixed.
 
 
It's easy to address the situation, though. Use the blank identifier to let unused things persist while you're developing.
 
 
What you may do is use the blank identifier when temporarily want to exclude something, e.g.
 
import (
    "fmt"
    _ "time"  // This will make the compiler stop complaining
)
 
 
 
Nowadays, most Go programmers use a tool, goimports, which automatically rewrites a Go source file to have the correct imports, eliminating the unused imports issue in practice. This program is easily connected to most editors to run automatically when a Go source file is written.