Re: Segmentation Fault - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Segmentation Fault
Date
Msg-id 3207310.1694737036@sss.pgh.pa.us
Whole thread Raw
In response to Re: Segmentation Fault  (Robert Sanford <wobbet@gmail.com>)
Responses Re: Segmentation Fault
List pgsql-bugs
Robert Sanford <wobbet@gmail.com> writes:
> I'm trying to get a core dump but I can't seem to actually generate one.
> ...
> I then restarted the postgres server. When I look at the limits in the pid
> folder I see...
> Limit                     Soft Limit           Hard Limit           Units
> Max cpu time              unlimited            unlimited            seconds
> Max file size             unlimited            unlimited            bytes
> Max data size             unlimited            unlimited            bytes
> Max stack size            8388608              unlimited            bytes
> Max core file size        0                    unlimited            bytes

This shows that you are now allowed to set "ulimit -c unlimited",
but you have not actually done so, at least not in the session that
you're using to inspect these settings.

If you are starting the server "by hand" (from a manual shell
command), it should work to do "ulimit -c unlimited" before issuing
the command to start the server.  If you are using infrastructure such
as systemd or initscripts, then you'll need to figure out how to get
it to set the ulimit in the environment of the server process.

BTW, have you tried disabling JIT to see if that stops the crashes?

            regards, tom lane



pgsql-bugs by date:

Previous
From: "Euler Taveira"
Date:
Subject: Re: Segmentation Fault
Next
From: PG Bug reporting form
Date:
Subject: BUG #18111: Query hangs when trying to INSERT empty string into NOT NULL table