From: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pggeneral <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Psycopg3 fails to resolve 'timezone localtime' on MacOS |
Date: | 2022-05-06 01:43:25 |
Message-ID: | 64199747-6DE1-4CF8-95BE-FA17B4A458C4@comcast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On May 5, 2022, at 8:29 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Jerry Sievers <gsievers19(at)comcast(dot)net> 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
> fragment is trying to set the PG server's timezone setting or
> not. Your issue may be purely a Python one.)
>
> Yep, understood.
Well the setting seems to be permitted for versions < 14.
Er, and we've got hundreds of them config'd as such presently.
More work to do.
I'm still curious though why it stopped working for Psycopg3.
Thx
> regards, tom lane
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jerry Sievers | 2022-05-06 01:54:42 | Re: Psycopg3 fails to resolve 'timezone localtime' on MacOS |
Previous Message | Daniele Varrazzo | 2022-05-06 01:43:17 | Re: Psycopg3 fails to resolve 'timezone localtime' on MacOS |