From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Daria Shanina <vilensipkdm(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: autoprewarm_dump_now |
Date: | 2025-06-03 17:17:43 |
Message-ID: | CA+TgmoYCMwr1BxE5ApJoxkqxrzSSvS509xqow4HY1-y90HjnJA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, May 30, 2025 at 6:07 AM Daria Shanina <vilensipkdm(at)gmail(dot)com> wrote:
> Some of our clients encountered a problem — they needed to allocate shared_buffers = 700 GB on a server with 1.5 TB RAM, and the error "invalid memory alloc request size 1835008000" occurred. That is, these are not mental exercises.
I think the proposed patch should be committed and back-patched, after
fixing it so that it's pgindent-clean and adding a comment. Does
anyone have strong objection to that?
--
Robert Haas
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2025-06-03 17:21:23 | Re: PG 18 release notes draft committed |
Previous Message | Jeff Davis | 2025-06-03 17:17:25 | Re: Persist injection points across server restarts |