Re: Do we need to back-patch tzcode 2026b after all?

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Do we need to back-patch tzcode 2026b after all?
Date: 2026-09-30 12:19:47
Message-ID: 85CA8500-000A-4686-9160-79F83E8129D4@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 30 Sep 2026, at 04:21, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Or we could just decide that we doubt any extensions
> are calling those directly, and accept the API/ABI break.

A very unscientific search using Debian codesearch and Github didn't reveal any
extensions with such callsites (which admittedly seems like a quite plausible
result).

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zsolt Parragi 2026-09-30 12:31:53 Re: injection_points: canceled or terminated waiters leak their wait slots
Previous Message Bertrand Drouvot 2026-09-30 12:19:15 Re: Persist slot invalidations before publishing them