| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: UTC is not a time zone? |
| Date: | 2024-05-13 18:36:12 |
| Message-ID: | 831534.1715625372@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Christophe Pettus <xof(at)thebuild(dot)com> writes:
>> On May 13, 2024, at 11:26, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rama Krishnan | 2024-05-14 07:57:47 | Valid until |
| Previous Message | Tom Lane | 2024-05-13 18:27:57 | Re: UTC is not a time zone? |