Jerry:
On Fri, 6 May 2022 at 03:04, Jerry Sievers wrote:
> Has anyone run into This?
> Psycopg3 fails to resolve timezone localtime on MacOS (Catalina).
>
> It falls back to UTC regardless of whether running with/without the
> tzdata package which I did try.
>
> There is a /
> On May 5, 2022, at 8:54 PM, Jerry Sievers wrote:
>
>
>
>> On May 5, 2022, at 8:43 PM, Daniele Varrazzo
>> wrote:
>>
>> On Fri, 6 May 2022 at 03:04, Jerry Sievers wrote:
>>>
>>> Has anyone run into This?
>>>
>
> On May 5, 2022, at 8:43 PM, Daniele Varrazzo
> wrote:
>
> On Fri, 6 May 2022 at 03:04, Jerry Sievers wrote:
>>
>> Has anyone run into This?
>>
>> Psycopg3 fails to resolve timezone localtime on MacOS (Catalina).
>
> That warning is typic
> On May 5, 2022, at 8:29 PM, Tom Lane wrote:
>
> Jerry Sievers writes:
>> Psycopg3 fails to resolve timezone localtime on MacOS (Catalina).
>
> I doubt Postgres will accept that zone name anywhere. It's
> not a standard name as far as the tzdb data set is conc
On Fri, 6 May 2022 at 03:04, Jerry Sievers wrote:
>
> Has anyone run into This?
>
> Psycopg3 fails to resolve timezone localtime on MacOS (Catalina).
That warning is typical on Windows, which doesn't have a system
timezone database, and on minimal Alpine installations, wher
Jerry Sievers writes:
> Psycopg3 fails to resolve timezone localtime on MacOS (Catalina).
I doubt Postgres will accept that zone name anywhere. It's
not a standard name as far as the tzdb data set is concerned.
(Having said that, it's far from clear to me whether this code
fragm
Has anyone run into This?
Psycopg3 fails to resolve timezone localtime on MacOS (Catalina).
It falls back to UTC regardless of whether running with/without the
tzdata package which I did try.
There is a /etc/localtime symlink on this box pointed at the correct
file in the tz data directory
