Re: Backporting BackgroundPsql

> On 25 Jun 2024, at 22:57, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Daniel Gustafsson <daniel@yesql.se> writes:
>> Before pulling any triggers I think https://commitfest.postgresql.org/48/4959/
>> should be considered, since Tom found some flaws in the current code around how
>> timers and timeouts are used.
>
> That's certainly another issue to consider, but is it really a blocker
> for this one?

It's not a blocker, but when poking at the code it seems useful to consider the
open items around it.

>> However, since Andrew is actively aiming to replace all of this shortly, should
>> we wait a see where that lands to avoid having to backport another library
>> change?
>
> I would like to see what he comes up with ... but is it likely to
> be something we'd risk back-patching?

Maybe it'll be a stretch given that it's likely to introduce new dependencies.

--
Daniel Gustafsson