| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | higherone(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17602: Query backend process killed because it uses up all memory. |
| Date: | 2022-08-30 19:01:31 |
| Message-ID: | 3727393.1661886091@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> I'm writing to seek for generic help on trouble shooting bugs related to
> query backend process killed because of memory exhaust on this single query
> process.
Try starting the server under a restrictive ulimit, so that it will
get ENOMEM failure before it bloats to the point of receiving an
OOM kill. Aside from being more friendly to other server processes,
this should result in getting a memory consumption map dumped to
postmaster stderr when the failure is hit. Seeing which context
is getting bloated would be pretty useful information.
On Linux I believe "ulimit -v" is the most appropriate setting to
change.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2022-08-31 05:30:31 | Re: pg_rewind WAL segments deletion pitfall |
| Previous Message | PG Bug reporting form | 2022-08-30 16:11:40 | BUG #17602: Query backend process killed because it uses up all memory. |