Changing parameter maintenance_work_mem = 10GB results in error Postgresql 17 #2374
Description
What version of osm2pgsql are you using?
osm2pgsql version 2.1.1
Build: RelWithDebInfo
Compiled using the following library versions:
Libosmium 2.22.0
Proj 9.6.0
Lua 5.4.7
What operating system and PostgreSQL/PostGIS version are you using?
Windows 11 Pro 24H2
Postgis bundle 3.5.3
Postgresql 17.5
Tell us something about your system
64GB RAM
AMD Ryzen 7 9800X3D
MSI MPG X870E CARBON WIFI (MS-7E49)
M2 disk for installation
What did you do exactly?
Stopped the postgresql service. Change the postgresql.conf parameters as advised on the osm2pgsql website and tried to restart the service
What did you expect to happen?
I expcted the postgresql just to work again when I restart the service.
What did happen instead?
I found out that changing the maintenance_work_mem into 10GB (as advised by osm2pgsql), postgresql doesnt get restarted. It gives the error 'connection refused getsockopt'
What did you do to try analyzing the problem?
Changing the parameter again in the default value .... and the service gets restarted! So far I have the value up to 256MB and the service still gets restarted, but there is a value that is too much for the system....