From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Julien Rouhaud <rjuju123(at)gmail(dot)com>, Don Seiler <don(at)seiler(dot)us>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Estimating HugePages Requirements? |
Date: | 2021-06-09 19:15:37 |
Message-ID: | 1428485.1623266137@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> I wonder how hard it would be to for example expose that through a
> commandline switch or tool.
Just try to start the server and see if it complains.
For instance, with shared_buffers=10000000 I get
2021-06-09 15:08:56.821 EDT [1428121] FATAL: could not map anonymous shared memory: Cannot allocate memory
2021-06-09 15:08:56.821 EDT [1428121] HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory, swap space, or huge pages. To reduce the request size (currently 83720568832 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections.
Of course, if it *does* start, you can do the other thing.
Admittedly, we could make that easier somehow; but if it took
25 years for somebody to ask for this, I'm not sure it's
worth creating a feature to make it a shade easier.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2021-06-09 19:23:50 | Re: Estimating HugePages Requirements? |
Previous Message | Magnus Hagander | 2021-06-09 19:07:09 | Re: Estimating HugePages Requirements? |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2021-06-09 19:23:50 | Re: Estimating HugePages Requirements? |
Previous Message | Tom Lane | 2021-06-09 19:07:48 | Re: Add PortalDrop in exec_execute_message |