From: Tom Lane <tgl@sss.pgh.pa.us>
To: PegoraroF10 <marcos@f10.com.br>
cc: pgsql-general@postgresql.org
Subject: Re: Server goes to Recovery Mode when run a SQL
In-reply-to: <1597265258319-0.post@n3.nabble.com>
References: <1549209182255-0.post@n3.nabble.com>
 <37bc715f-12e2-84ac-6492-88d7b6306777@aklaver.com>
 <1549211574297-0.post@n3.nabble.com>
 <cfcb3858-d169-652c-71a7-5d77f295085a@aklaver.com>
 <20190204010709.GC1881@paquier.xyz> <1597265258319-0.post@n3.nabble.com>
Comments: In-reply-to PegoraroF10 <marcos@f10.com.br>
	message dated "Wed, 12 Aug 2020 13:47:38 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <323344.1597270142.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 12 Aug 2020 18:09:02 -0400
Message-ID: <323345.1597270142@sss.pgh.pa.us>
Precedence: bulk

PegoraroF10 <marcos@f10.com.br> writes:
> Hi Michael, so sorry for the delay. I did never had that problem again, =
so
> tougth it was solved, but seems not. We have two different SQL which pus=
hs
> server to recovery mode. This SQL is the hardest one, because you=C2=B4l=
l have to
> wait some time to get the error. Just runs this SQL, opens your HTOP and
> wait, you=C2=B4ll see your memory growing and growing until ... =


Are you sure this query ever terminates?  It looks to me like it just
keeps producing tuples indefinitely until you kill it or something runs
out of memory.

If the response to "out of memory" is a server crash rather than something
nicer, you probably need to corral your OOM killer.  See

https://www.postgresql.org/docs/current/kernel-resources.html#LINUX-MEMORY=
-OVERCOMMIT

			regards, tom lane