Re: Inconsistent time zone output for JSON at UTC

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Gregory Jensen <GreatDJonfire(at)hotmail(dot)co(dot)uk>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Inconsistent time zone output for JSON at UTC
Date: 2022-05-31 12:00:34
Message-ID: CAKFQuwaDa9R9SKhKS8t4RsKto0rXK3EHjbcv6QUEso3oeLzL_w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tuesday, May 31, 2022, Gregory Jensen <GreatDJonfire(at)hotmail(dot)co(dot)uk>
wrote:
>
>
> When the server time zone setting is UTC - timezone = 'UTC'
>
> select to_json(created_at::timestamptz) from test_tz;
> to_json
> ------------------------------------
> "2022-05-31T10:20:07.133799+00:00"
> (1 row)
>

This is the solution. The timezone setting isn't a “server setting”, it is
a session-local setting with an initial value based upon server
configuration. Change it for the session to UTC if you for some reason
must output +00.

The at time zone operator outputs a timestamp without timezone and that is
why those variants don’t produce any time zone offset.

David J.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2022-05-31 12:03:17 Re: BUG #17485: Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY
Previous Message Fabien COELHO 2022-05-31 11:51:07 Re: psql 15beta1 does not print notices on the console until transaction completes