Re: PostgreSQL 17.5 - could not map dynamic shared memory segment

2025-06-21 Thread Tomas Vondra
On 6/21/25 23:09, Aleš Zelený wrote: > Hello, > ... > > The application benefits from parallel queries, so despite the first > temptation to disable parallel queries (based on log entries correlation > only, but is that the root cause?) I did not want to disable parallel > queries, if there is anot

PostgreSQL 17.5 - could not map dynamic shared memory segment

2025-06-21 Thread Aleš Zelený
Hello, After upgrading from (old good no longer supported Pg11) to PostgreSQL 17.5 via pg_dump & pg_restore vacuum started reporting errors: ERROR: could not map dynamic shared memory segment Vacuumdb was invoked: /usr/lib/postgresql/17/bin/vacuumdb -p 5433 -Fvaz -j 12 -v The vacuum finished