From: Tom Lane <tgl@sss.pgh.pa.us>
To: =?UTF-8?B?0JDQvdGC0L7QvSDQk9C70YPRiNCw0LrQvtCy?= <a.glushakov86@gmail.com>
cc: pgsql-admin@lists.postgresql.org
Subject: Re: pg_dump --binary-upgrade out of memory
In-reply-to: 
 <CAHnOmaeCZN0tOEfmu3VOLjDujfY2jbS0HaEfwTboY1knhfwzvQ@mail.gmail.com>
References: 
 <CAHnOmaeCZN0tOEfmu3VOLjDujfY2jbS0HaEfwTboY1knhfwzvQ@mail.gmail.com>
Comments: In-reply-to =?UTF-8?B?0JDQvdGC0L7QvSDQk9C70YPRiNCw0LrQvtCy?=
 <a.glushakov86@gmail.com>
	message dated "Mon, 12 Feb 2024 18:36:20 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2658641.1707849008.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 13 Feb 2024 13:30:08 -0500
Message-ID: <2658642.1707849008@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2658642.1707849008%40sss.pgh.pa.us>
Precedence: bulk

=3D?UTF-8?B?0JDQvdGC0L7QvSDQk9C70YPRiNCw0LrQvtCy?=3D <a.glushakov86@gmail.=
com> writes:
> I encountered the problem of not being able to upgrade my instance (14->=
15)
> via pg_upgrade.
> The utility crashed with an error in out of memory.
> After researching a bit I found that this happens at the moment of expor=
t
> schema  with pg_dump.
> Then I tried to manually perform a dump schema with the parameter
> --binary-upgrade option and also got an out of memory.
> Digging a little deeper, I discovered quite a large number of blob objec=
ts
> in the database (pg_largeobject 10GB and pg_largeobject_metadata 1GB (31=
kk
> rows))

Yeah, dumping a database with a lot of blobs is a known pain point.

I have some patches in progress that intend to make that better [1],
but they're meant for v17 and I'm not sure if you could get them to
work in v15.  In the meantime, trying to run pg_dump on a beefier
machine might be your best option.

			regards, tom lane

[1] https://commitfest.postgresql.org/47/4713/