Re: autoprewarm_dump_now - Mailing list pgsql-hackers

From Daria Shanina
Subject Re: autoprewarm_dump_now
Date
Msg-id CAMp4U1c8S7oTsuNahvkFLR7OeSxnamtOHgey=rcMi=Y7cWg7ng@mail.gmail.com
Whole thread Raw
In response to Re: autoprewarm_dump_now  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: autoprewarm_dump_now
List pgsql-hackers

Hello!

I have made a patch, now we can allocate more than 1 GB of memory for the autoprewarm_dump_now function.


Best regards,

Daria Shanina


пт, 4 апр. 2025 г. в 19:36, Robert Haas <robertmhaas@gmail.com>:
On Fri, Apr 4, 2025 at 12:17 PM Melanie Plageman
<melanieplageman@gmail.com> wrote:
> Unrelated to this problem, but I wondered why autoprewarm doesn''t
> launch background workers for each database simultaneously instead of
> waiting for each one to finish a db before moving onto the next one.
> Is it simply to limit the number of bgworkers taking up resources?

That's probably part of it, but also (1) a system that allowed for
multiple workers would be somewhat more complex to implement and (2)
I'm not sure how beneficial it would be. We go to some trouble to make
the I/O as sequential as possible, and this would detract from that. I
also don't know how long prewarming normally takes -- if it's fast
enough already, then maybe this doesn't matter. But if somebody is
having a problem with autoprewarm being slow and wants to implement a
multi-worker system to make it faster, cool.

--
Robert Haas
EDB: http://www.enterprisedb.com


Attachment

pgsql-hackers by date:

Previous
From: Matheus Alcantara
Date:
Subject: Re: Fixing memory leaks in postgres_fdw
Next
From: Tom Lane
Date:
Subject: Re: Fixing memory leaks in postgres_fdw