On Sun, Apr 02, 2023 at 04:37:38PM -0400, Tom Lane wrote:
> Nathan Bossart <nathandbossart@gmail.com> writes:
>> It's been a little while since I dug into this, but I do see your point
>> that the wraparound risk could be higher in some cases. For example, if
>> you have a billion temp files to clean up, the custodian could be stuck on
>> that task for a long time. I will give this some further thought. I'm all
>> ears if anyone has ideas about how to reduce this risk.
>
> I wonder if a single long-lived custodian task is the right model at all.
> At least for RemovePgTempFiles, it'd make more sense to write it as a
> background worker that spawns, does its work, and then exits,
> independently of anything else. Of course, then you need some mechanism
> for ensuring that a bgworker slot is available when needed, but that
> doesn't seem horridly difficult --- we could have a few "reserved
> bgworker" slots, perhaps. An idle bgworker slot doesn't cost much.
This has crossed my mind. Even if we use the custodian for several
different tasks, perhaps it could shut down while not in use. For many
servers, the custodian process will be used sparingly, if at all. And if
we introduce something like custodian_max_workers, perhaps we could dodge
the wraparound issue a bit by setting the default to the number of
supported tasks. That being said, this approach adds some complexity.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com