From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christophe Pettus <xof@thebuild.com>
cc: Adrian Klaver <adrian.klaver@aklaver.com>,
        "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Subject: Re: UTC is not a time zone?
In-reply-to: <38C9B285-5F4B-4A94-BD34-6FE275A35A39@thebuild.com>
References: <327870A4-F35C-462C-9F64-E0838374AFDF@thebuild.com> <63e65356-9cb5-48b7-9bc5-5c734013ebe1@aklaver.com> <C430EBE1-EFA9-407D-8830-7C379B24B5AB@thebuild.com> <828310.1715624225@sss.pgh.pa.us> <8DA3DC1C-E406-4921-8A86-A83BF140E13D@thebuild.com> <f7c272a0-8feb-41c0-bc6e-ffb922c2c160@aklaver.com> <38C9B285-5F4B-4A94-BD34-6FE275A35A39@thebuild.com>
Comments: In-reply-to Christophe Pettus <xof@thebuild.com>
	message dated "Mon, 13 May 2024 11:27:34 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <831533.1715625372.1@sss.pgh.pa.us>
Date: Mon, 13 May 2024 14:36:12 -0400
Message-ID: <831534.1715625372@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/831534.1715625372%40sss.pgh.pa.us>
Precedence: bulk

Christophe Pettus <xof@thebuild.com> writes:
>> On May 13, 2024, at 11:26, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
>> May not induce the error unless there are parallel workers involved.

> Indeed.  I'll see about pulling together a test case that forces that.

Right.  Once a backend process has loaded a zone file, it caches that
in a hash table that it will never flush (which is arguably a bug for
other reasons, since those files aren't really immutable, but that's
how it behaves today).  So you've got 0 chance of hitting this via
repeat SET TIMEZONE in a single backend.

			regards, tom lane