From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Lincoln Swaine-Moore <lswainemoore(at)gmail(dot)com> |
Cc: | Marian Wendt <marian(dot)wendt(at)yahoo(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Strategies for converting UTC data to local windows for arbitrary resolutions and timezones |
Date: | 2023-10-04 17:40:16 |
Message-ID: | 2608036.1696441216@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Lincoln Swaine-Moore <lswainemoore(at)gmail(dot)com> writes:
>> Yeah. One thing to keep in mind is that that might have different
>> behavior in terms of the evaluation of the arguments to the function,
>> ie which timezone setting is your input parsed according to.
> I see. You mean, in the event that it doesn't conform to an entry in
> `pg_timezone_names`? I do have control over the possible options the user
> can provide, so it should be straightforward to make sure those all have
> entries.
If you mean that your input will always include an explicit zone
specification, then this doesn't affect you. What I was thinking
about was that
select generate_series('2023-10-04 13:30', ...)
is going to mean different things depending on the zone setting
that prevails when that constant is parsed.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Lincoln Swaine-Moore | 2023-10-04 17:45:33 | Re: Strategies for converting UTC data to local windows for arbitrary resolutions and timezones |
Previous Message | Lincoln Swaine-Moore | 2023-10-04 17:35:51 | Re: Strategies for converting UTC data to local windows for arbitrary resolutions and timezones |