Re: autoprewarm_dump_now
| От | Daria Shanina |
|---|---|
| Тема | Re: autoprewarm_dump_now |
| Дата | |
| Msg-id | CAMp4U1doDjku1675GRRtpwML2aGsYqjC0SZBm7xozGfQiBfCug@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: autoprewarm_dump_now (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: autoprewarm_dump_now
|
| Список | pgsql-hackers |
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.
Best regards,
Daria Shanina
чт, 29 мая 2025 г. в 16:21, Tom Lane <tgl@sss.pgh.pa.us>:
Daria Shanina <vilensipkdm@gmail.com> writes:
> I have made a patch, now we can allocate more than 1 GB of memory for the
> autoprewarm_dump_now function.
Is that solving a real-world problem? If it is, shouldn't we be
looking for a different approach that doesn't require such a huge
amount of memory?
regards, tom lane
С уважением,
Шанина Дарья Александровна
В списке pgsql-hackers по дате отправления: