Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1uKdCw-0085Ig-Lr
	for pgsql-hackers@arkaria.postgresql.org; Thu, 29 May 2025 13:22:06 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1uKdCv-008zRn-Cr
	for pgsql-hackers@arkaria.postgresql.org; Thu, 29 May 2025 13:22:05 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1uKdCv-008zRQ-3d
	for pgsql-hackers@lists.postgresql.org; Thu, 29 May 2025 13:22:05 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by makus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1uKdCt-000XtX-1R
	for pgsql-hackers@lists.postgresql.org;
	Thu, 29 May 2025 13:22:04 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 54TDLmFM1876465;
	Thu, 29 May 2025 09:21:48 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daria Shanina <vilensipkdm@gmail.com>
cc: Robert Haas <robertmhaas@gmail.com>,
        Melanie Plageman <melanieplageman@gmail.com>,
        Heikki Linnakangas <hlinnaka@iki.fi>,
        pgsql-hackers@lists.postgresql.org
Subject: Re: autoprewarm_dump_now
In-reply-to: 
 <CAMp4U1c8S7oTsuNahvkFLR7OeSxnamtOHgey=rcMi=Y7cWg7ng@mail.gmail.com>
References: 
 <CAMp4U1cDJzb96KJXT-hNuf7L4KaYUiXWs6KSe01so--mBoop8g@mail.gmail.com>
 <71abd264-1911-46a0-a25b-079a7cfa577a@iki.fi>
 <CAAKRu_YyuqbRaVO-zkoeRLFeNtF_jX-faGSGH4h3JB6ckORWMg@mail.gmail.com>
 <CA+TgmobRMXwFg4AUZ96FvXALFkN8H7KBqhCp-CtMS83RuKXG3A@mail.gmail.com>
 <CAMp4U1c8S7oTsuNahvkFLR7OeSxnamtOHgey=rcMi=Y7cWg7ng@mail.gmail.com>
Comments: In-reply-to Daria Shanina <vilensipkdm@gmail.com>
	message dated "Thu, 29 May 2025 16:16:13 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1876463.1748524908.1@sss.pgh.pa.us>
Date: Thu, 29 May 2025 09:21:48 -0400
Message-ID: <1876464.1748524908@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: 
 <https://www.postgresql.org/message-id/1876464.1748524908%40sss.pgh.pa.us>
Precedence: bulk

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