| From: | Daria Shanina <vilensipkdm(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, 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-05-30 10:07:37 |
| Message-ID: | CAMp4U1doDjku1675GRRtpwML2aGsYqjC0SZBm7xozGfQiBfCug@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)sss(dot)pgh(dot)pa(dot)us>:
> Daria Shanina <vilensipkdm(at)gmail(dot)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
>
--
С уважением,
Шанина Дарья Александровна
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zhijie Hou (Fujitsu) | 2025-05-30 10:07:42 | RE: Replication slot is not able to sync up |
| Previous Message | Nisha Moond | 2025-05-30 09:30:30 | Re: Fix slot synchronization with two_phase decoding enabled |