Re: autoprewarm_dump_now

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Daria Shanina <vilensipkdm(at)gmail(dot)com>
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-29 13:21:48
Message-ID: 1876464.1748524908@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Timur Magomedov 2025-05-29 13:30:23 Re: [WIP]Vertical Clustered Index (columnar store extension) - take2
Previous Message Tom Lane 2025-05-29 13:17:52 Re: Fixing memory leaks in postgres_fdw