Bharanee Rathna writes:
> To be more specific, I expected the output of both these queries to be the
> same.
> # select '2017-12-01 11:00:00 +11:00'::timestamp with time zone at time
> zone '+11:00';
> # select '2017-12-01 11:00:00 +11:00'::timestamp with time zone at time
> zone 'Australia/Melbou
On Mon, 2017-12-04 at 14:03 +1100, Bharanee Rathna wrote:
> To be more specific, I expected the output of both these queries to
> be the same.
>
> # select '2017-12-01 11:00:00 +11:00'::timestamp with time zone at
> time zone '+11:00';
> timezone
> -
> 2017-11-3
To be more specific, I expected the output of both these queries to be the
same.
# select '2017-12-01 11:00:00 +11:00'::timestamp with time zone at time
zone '+11:00';
timezone
-
2017-11-30 13:00:00
# select '2017-12-01 11:00:00 +11:00'::timestamp with time zone at
Sorry I didn't mean for it to come out as a complaint, just that I am
confused since the result of the SQL query was not what I expected. I
expected +11:00 to be 11 hours east of UTC which wasn't the case.
On 4 December 2017 at 13:55, Tom Lane wrote:
> Bharanee Rathna writes:
> > the document
Bharanee Rathna writes:
> the documentation around how numeric offsets are parsed from strings is a
> bit confusing, are they supposed to be treated as ISO8601 or POSIX ?
Our documentation about this says clearly that Postgres considers offsets
to be ISO (positive-east-of-Greenwich) everywhere ex
Hi,
the documentation around how numeric offsets are parsed from strings is a
bit confusing, are they supposed to be treated as ISO8601 or POSIX ?
e.g.
select '2017-12-01 11:00:00 +11:00'::timestamp with time zone at time zone
'+11:00';
timezone
-
2017-11-30 13:00:0
