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
