On Mon, Sep 3, 2018 at 09:20:34AM -0400, Bruce Momjian wrote:
> On Sun, Sep 2, 2018 at 10:11:59PM -0400, Bruce Momjian wrote:
> > On Sun, Sep 2, 2018 at 02:21:58PM -0400, Tom Lane wrote:
> > > I still find this to be more confusing than helpful. In particular,
> > > I do not think that it's
fOn Sun, Sep 2, 2018 at 02:21:58PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > ! The AT TIME ZONE construct allows the addition,
> > ! conversion, and removal of time zones for time stamp values. > linkend="functions-datetime-zoneconvert-table"/> shows its
> >
On Sat, Sep 1, 2018 at 07:37:36PM -0400, Bruce Momjian wrote:
> > Here we've got a time value that was initially given in EST (-05),
> > but was converted to UTC by timestampz_in. Then the AT TIME ZONE
> > says "Please convert this UTC value to MST, and emit it as a zoneless
> > timestamp"
On Sat, Sep 1, 2018 at 07:30:43PM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > Looking over the AT TIME ZONE docs, I think they are subtly confusing.
> > The order of conversion specific in the first example should _start_
> > with the assumption of local time zone for the time stamp, not
Bruce Momjian writes:
> Looking over the AT TIME ZONE docs, I think they are subtly confusing.
> The order of conversion specific in the first example should _start_
> with the assumption of local time zone for the time stamp, not something
> that happens after AT TIME ZONE is applied. The
Looking over the AT TIME ZONE docs, I think they are subtly confusing.
The order of conversion specific in the first example should _start_
with the assumption of local time zone for the time stamp, not something
that happens after AT TIME ZONE is applied. The ordering in current
docs makes the