[Tile-serving] [osm2pgsql-dev/osm2pgsql] Changing parameter maintenance_work_mem = 10GB results in error Postgresql 17 (Discussion #2375)

[mboeringa]

> I simply seems there is a limit to how large `work_mem` and `maintenance_work_mem` can be on Windows. A limit that's not there on Linux. See for instance [here](https://stackoverflow.com/questions/33995367/cannot-increase-work-mem-above-1gb-using-postgresql-9-3-on-windows-server) and [here](https://www.reddit.com/r/PostgreSQL/comments/u17gwb/why_i_cant_set_working_memory_more_than_1gb_it/). I don't know why there is this limit and why it isn't documented in the PostgreSQL manual and whether that's something that depends on the PostgreSQL version.

>I can confirm that maintenance_work_mem on 1024MB is ok, but 2048 gives the above mentioned error. Maybe it's good to state that in the manual

I doubt this is a Windows issue. Maybe @pimmierevrev has forgotten to allocate Windows virtual memory though on his machine, to allow some more wiggle room for Windows to deal with memory issues. 

As @ImreSamu justly pointed out, this is most likely simply a misconfigured PostgreSQL instance, that doesn't properly take into account the (limited) server's resources. There is little sense in adjusting the osm2pgsql documentation for that, users should consult the PostgreSQL docs instead.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/osm2pgsql-dev/osm2pgsql/discussions/2375#discussioncomment-14091136
You are receiving this because you are subscribed to this thread.

Message ID: <osm2pgsql-dev/osm2pgsql/repo-discussions/2375/comments/14091136 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20250813/5a86e30a/attachment.htm>