| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Erik Rijkers" <er(at)xs4all(dot)nl> |
| Cc: | "Christian Kruse" <christian(at)2ndQuadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, teodor(at)sigaev(dot)ru, obartunov(at)gmail(dot)com, andrew(at)dunslane(dot)net |
| Subject: | Re: nested hstore - large insert crashes server |
| Date: | 2014-02-04 19:14:59 |
| Message-ID: | 27718.1391541299@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Erik Rijkers" <er(at)xs4all(dot)nl> writes:
> On Tue, February 4, 2014 18:56, Christian Kruse wrote:
>> Did you check if this was the OOM killer? Should be logged in dmesg.
> I would be surprised if it wasn't. (no access to that machine at the moment)
> How do we regard such crashes? It seems to me this was rather eaasily 'provoked' (for want of a better word).
Well, it suggests that there may be a memory leak, which would be a bug
even though we'd assign it lower priority than a true crash.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2014-02-04 19:15:54 | Re: PQputCopyData dont signal error |
| Previous Message | Andres Freund | 2014-02-04 19:11:18 | Re: Performance Improvement by reducing WAL for Update Operation |