From: Tom Lane <tgl@sss.pgh.pa.us>
To: Siraj G <tosiraj.g@gmail.com>
cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Out of Memory error triggering replica to transition into
 recovery mode
In-reply-to: 
 <CAC5iy61uGHGfLpR2Wded8ZniyKqREeDBdeJ4ryXZ5jwU6-oKyg@mail.gmail.com>
References: 
 <CAC5iy61uGHGfLpR2Wded8ZniyKqREeDBdeJ4ryXZ5jwU6-oKyg@mail.gmail.com>
Comments: In-reply-to Siraj G <tosiraj.g@gmail.com>
	message dated "Thu, 28 Nov 2024 08:34:57 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2092966.1732811482.1@sss.pgh.pa.us>
Date: Thu, 28 Nov 2024 11:31:22 -0500
Message-ID: <2092967.1732811482@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2092967.1732811482%40sss.pgh.pa.us>
Precedence: bulk

Siraj G <tosiraj.g@gmail.com> writes:
> As the subject says, today very frequently our replica DB is going into the
> recovery mode causing an outage in the application side.

If you're not on this month's minor releases, perhaps you should be:

    Reduce memory consumption of logical decoding (Masahiko Sawada)

        Use a smaller default block size to store tuple data received
        during logical replication. This reduces memory wastage, which
        has been reported to be severe while processing long-running
        transactions, even leading to out-of-memory failures.

I recall past updates that fixed other memory leaks in logical
replication, too.

> Pgsql: 12.2

Egad.  Your version-updating strategy seriously needs a rethink.

			regards, tom lane