Date: Mon, 13 May 2024 19:53:19 +0200
From: Erik Wienhold <ewie@ewie.name>
To: Christophe Pettus <xof@thebuild.com>
Cc: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Subject: Re: UTC is not a time zone?
Message-ID: <b79c1b73-33f6-4115-a382-31836925b5fa@ewie.name>
References: <327870A4-F35C-462C-9F64-E0838374AFDF@thebuild.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <327870A4-F35C-462C-9F64-E0838374AFDF@thebuild.com>
Archived-At: <https://www.postgresql.org/message-id/b79c1b73-33f6-4115-a382-31836925b5fa%40ewie.name>
Precedence: bulk

On 2024-05-13 19:37 +0200, Christophe Pettus wrote:
> PostgreSQL 16.3 on MacOS Sonoma.  A long-running process (which held a
> connection open the entire time) failed with:
> 
> 2024-05-13 09:12:44.719 PDT,"cyan","cyan",35926,"[local]",664214f9.8c56,3,"SELECT",2024-05-13 06:26:17 PDT,3/444460,0,ERROR,22023,"invalid value for parameter ""TimeZone"": ""UTC""",,,,,"while setting parameter ""TimeZone"" to ""UTC""
> parallel worker","  select count(1), count(1) filter (where visited > 0) from framework_seenchoice  ",,,"","client backend",,0
> 
> It's not (easily) repeatable, and the system was not touched while the
> process was running (no installing new binaries, etc.).  Does this
> look familiar to anyone?

Could be the same issue as [1] (also on macOS).

Can you trigger that error with:

    SET timezone = 'UTC';

And what's the output of:

    SELECT * FROM pg_timezone_names ORDER BY name;

[1] https://www.postgresql.org/message-id/5DF49366-10D1-42A4-99BF-F9A7DC3AB0F4%40mailbox.org

-- 
Erik