| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Tomas Vondra <tomas(at)vondra(dot)me>, Andres Freund <andres(at)anarazel(dot)de>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Bernd Helmle <mailings(at)oopsware(dot)de>, Michael Banck <mbanck(at)gmx(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Changing the state of data checksums in a running cluster |
| Date: | 2026-08-26 22:05:28 |
| Message-ID: | AC614284-3C0C-4CA2-880F-E1B109519182@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 24 Aug 2026, at 12:00, Alexander Lakhin <exclusion(at)gmail(dot)com> wrote:
>>> I've modified the TAP tests to add
>>>
>>> max_worker_processes = 16
>>> max_parallel_workers = 16
>>>
>>> and with that change it passes just fine.
>
> Yeah, these settings work for me too.
>
>> One option would be debug_parallel_query = off to shave the number of
>> workers spawned.
>
> Yes, there are a couple of tests that do this already
This admittedly seems like the best fix here.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zsolt Parragi | 2026-08-26 22:06:20 | Re: datachecksums: handle invalid and dropped databases during enable |
| Previous Message | Daniel Gustafsson | 2026-08-26 22:02:46 | Re: datachecksums: handle invalid and dropped databases during enable |