| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | PegoraroF10 <marcos(at)f10(dot)com(dot)br> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Server goes to Recovery Mode when run a SQL |
| Date: | 2020-08-12 22:09:02 |
| Message-ID: | 323345.1597270142@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
PegoraroF10 <marcos(at)f10(dot)com(dot)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 pushs
> server to recovery mode. This SQL is the hardest one, because you´ll have to
> wait some time to get the error. Just runs this SQL, opens your HTOP and
> wait, you´ll 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | raf | 2020-08-12 23:38:11 | Re: Implement a new data type |
| Previous Message | Shankar Bhaskaran | 2020-08-12 20:54:10 | psql and jdbc default sslmode |