| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Recent "could not register background process" buildfarm failures |
| Date: | 2026-08-18 17:44:32 |
| Message-ID: | aoSZSImNRBnWrLhW@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"La persona que no quería pecar / estaba obligada a sentarse
en duras y empinadas sillas / desprovistas, por cierto
de blandos atenuantes" (Patricio Vogel)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2026-08-18 18:01:25 | Re: pgstat: Flush some statistics within running transactions, take 2 |
| Previous Message | Bharath Rupireddy | 2026-08-18 17:43:00 | Re: [Patch] Omit virtual generated columns from test_decoding output |