Re: Changing displayed time zone in RAISE NOTICE output?

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Changing displayed time zone in RAISE NOTICE output?
Date: 2023-01-12 16:22:33
Message-ID: CAFj8pRA9QjKgDO+4JP0OwB4C2acSD=BPmF2R2VEutF4n0-UKwg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

čt 12. 1. 2023 v 16:39 odesílatel Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
napsal:

> On 1/11/23 21:25, Ron wrote:
> > On 1/11/23 15:06, Adrian Klaver wrote:
>
> >
> > Hmm. I'd have sworn this didn't work when I tried it:
>
> Did you do?:
>
> DO $$
> BEGIN
> RAISE NOTICE '%', clock_timestamp() at timezone 'UTC';
> END$$;
> ERROR: syntax error at or near "timezone"
> LINE 3: RAISE NOTICE '%', clock_timestamp() at timezone 'UTC';
>
>
there should be space >>AT TIME ZONE<<

(2023-01-12 17:21:10) postgres=# DO $$
BEGIN
RAISE NOTICE '%', clock_timestamp() at time zone 'UTC';
END$$;
NOTICE: 2023-01-12 16:21:14.063256
DO
(2023-01-12 17:21:14) postgres=#

>
> >
> > postgres=#
> > postgres=# DO $$
> > BEGIN
> > RAISE NOTICE '%', clock_timestamp() at time zone 'UTC';
> > END$$;
> > NOTICE: 2023-01-12 05:22:40.517299
> >
> > But it does work, so all's well that ends well.
> >
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
>
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dimitrios Apostolou 2023-01-12 16:24:20 Why is a hash join preferred when it does not fit in work_mem
Previous Message Adrian Klaver 2023-01-12 15:38:54 Re: Changing displayed time zone in RAISE NOTICE output?