pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: wobbet@wobbet.com, Robert Sanford <wobbet@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Segmentation Fault
Date: Thu, 14 Sep 2023 20:17:16 -0400
Message-ID: <3207310.1694737036@sss.pgh.pa.us> (raw)
In-Reply-To: <CABa+nRs8vLBkCtSw5HJCreo1Fx-NysHG_AgMBBOQNBFFGnwQJA@mail.gmail.com>
References: <CABa+nRvwZy_5t1QF9NJNGwAf03tv_PO_Sg1FsN1+-3Odb1XgBA@mail.gmail.com>
	<CABa+nRuatSjnqsPfnoo0APzgeM1Um94FesYj6H1YKB1qJ8JoqA@mail.gmail.com>
	<3030992.1694649537@sss.pgh.pa.us>
	<CABa+nRs0x9DR52xyRa2COJOad-9VfjYQkDRcJOPACGsSCN_QJQ@mail.gmail.com>
	<CABa+nRs8vLBkCtSw5HJCreo1Fx-NysHG_AgMBBOQNBFFGnwQJA@mail.gmail.com>

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





view thread (10+ messages)  latest in thread

Message-ID: <3207310.1694737036@sss.pgh.pa.us>
Permalink:  ../3207310.1694737036@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3207310.1694737036@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, wobbet@gmail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: Segmentation Fault
  In-Reply-To: <3207310.1694737036@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox