| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Recent "could not register background process" buildfarm failures |
| Date: | 2026-08-18 20:47:44 |
| Message-ID: | 99E27A7C-5BC8-4DC7-B6BB-D35B0679C884@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 18 Aug 2026, at 19:44, Álvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:
>
> On 2026-Aug-18, Tom Lane wrote:
>
>> # +ERROR: could not register background process
>> # +HINT: You may need to increase "max_worker_processes".
>>
>> test_shm_mq itself hasn't changed meaningfully in ages,
>> so it seems like some recent change somewhere else has increased
>> the probability of not being able to get a worker process.
>> Maybe autovacuum is eating too many workers? Any thoughts?
>
> Hm, autovacuum does not use workers from the bgworker pool AFAIK.
> Repack concurrently does. However, I don't think we use repack
> concurrently anywhere in the standard tests; we only run it in the
> test_decoding and injection_point tests, which have separate instances.
Online checksums also use bgworkers but it too should not be running here, and
looking at it I didn't see evidence of it interfering. I'll have another look
in the morning with fresh eyes.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2026-08-18 20:59:59 | Re: [Patch] Omit virtual generated columns from test_decoding output |
| Previous Message | Peter Geoghegan | 2026-08-18 20:32:31 | Re: gistkillitems can LP_DEAD-mark the wrong tuples on a rescan |