From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Alban Hertroys <haramrae(at)gmail(dot)com> |
Cc: | Alban Hertroys <a(dot)hertroijs(at)nieuwestroom(dot)nl>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Time zone offset in to_char() |
Date: | 2024-01-11 21:15:44 |
Message-ID: | e0166046-fabf-49c4-a754-b0868e003563@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 1/11/24 11:04, Alban Hertroys wrote:
>
> I did manage to apply it to the second function header, which I think behaves such that the time zone change stays within function scope. Right now I’m not 100% sure that I verified that. More to check tomorrow.
CREATE OR REPLACE FUNCTION public.tz_fnc2()
RETURNS void
LANGUAGE plpgsql
SET "TimeZone" TO 'UTC'
AS $function$
BEGIN
RAISE NOTICE '%', to_char(now(), 'OF');
END;
$function$;
test=# begin ;
BEGIN
test=*# select public.tz_fnc2();
NOTICE: +00
tz_fnc2
---------
(1 row)
test=*# show timezone;
TimeZone
----------
UTC
(1 row)
test=*# commit ;
COMMIT
test=# show timezone;
TimeZone
----------
UTC
(1 row)
>
> Frankly, I do hope that you’re right here, that would make my work easier.
>
> Alban Hertroys
> --
> If you can't see the forest for the trees,
> cut the trees and you'll find there is no forest.
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2024-01-11 21:40:46 | Re: Refresh Materialized View Issue |
Previous Message | Adrian Klaver | 2024-01-11 21:09:00 | Re: Time zone offset in to_char() |