| From: | Feike Steenbergen <feikesteenbergen(at)gmail(dot)com> |
|---|---|
| To: | josef(dot)machytka(at)gmail(dot)com |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14845: postgres_fdw and mysql_fdw can cause crash of instance |
| Date: | 2017-10-06 13:04:33 |
| Message-ID: | CAK_s-G0RMp_J0iL+sVYFaAASL_vLqrmk27PqDFfAdJM0M8QHfA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 6 October 2017 at 13:24, <josef(dot)machytka(at)gmail(dot)com> wrote:
> After that in first case postgresql crashed (which was more or less OK
> because it restarted) but in second case the whole Debian instance crashed
What causes the crash, is it the out-of-memory (OOM) killer?
How have you configured overcommit on your Debian instance?
https://www.postgresql.org/docs/current/static/kernel-resources.html#linux-memory-overcommit
If it is the OOM killer killing your process, you may want to disable
overcommit. Doing that should cause the client to get a decent error
message instead of the the whole cluster being restarted.
regards,
Feike
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabrízio de Royes Mello | 2017-10-06 13:29:29 | Re: BUG #14845: postgres_fdw and mysql_fdw can cause crash of instance |
| Previous Message | josef.machytka | 2017-10-06 11:24:26 | BUG #14845: postgres_fdw and mysql_fdw can cause crash of instance |