| From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | tom(at)quist(dot)de, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17793: Query with large number of joins crashes PostgreSQL |
| Date: | 2023-02-14 16:35:03 |
| Message-ID: | CA+bJJbyxXx-s5Ur2nxEvpzWuGtAuNEe5f=PE7axPQaH2jcmxgQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi Tom:
On Tue, 14 Feb 2023 at 15:47, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> If overcommit-disabled doesn't seem practical, another idea that's
> been recommended is to start the postmaster under a "ulimit -v"
> setting chosen to cause plain ENOMEM failures before the OOM
> killer kicks in.
This may certainly help, but if I read the oomkiller stuff correctly
you can have a case where Pg has its (big) share of memory allocated
and commited, some other processes have overallocated and have
uncommitted memory and when one of these tries to commit some mem the
OOM kills Pg because it is the biggest memory user. Not an covercommti
fan, so not too sure.
FOS
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2023-02-14 19:19:37 | Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently |
| Previous Message | Tom Lane | 2023-02-14 16:26:51 | Re: BUG #17782: ERROR: variable not found in subplan target lists |