Christophe Pettus <xof@thebuild.com> writes:
> On May 13, 2024, at 10:48, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
>> https://www.postgresql.org/message-id/1273542.1712326418%40sss.pgh.pa.us
> Thanks! Similar, but I don't think it's that. This was a sudden change in a long-running connection that had issued
aton of ` SET TIMEZONE TO 'UTC'; ` before the failure.
The underlying cause is likely roughly similar, to wit failure to read
/usr/share/zoneinfo/UTC (or the Postgres-private equivalent file).
The parent process would long since have cached the zone data in its
memory, but this error is in a parallel worker process, which'd have
to read the file for itself during startup.
What's causing that I can't say. It doesn't look like we log the
errno anywhere when failing to read a zone file :-(
regards, tom lane
