pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: S Bob <sbob@quadratum-braccas.com>
Cc: Peter Geoghegan <pg@bowt.ie>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: How to analyze a core dump
Date: Mon, 02 Nov 2020 13:04:06 -0500
Message-ID: <686892.1604340246@sss.pgh.pa.us> (raw)
In-Reply-To: <293bf7b3-9fe0-e49e-eaee-031aaf11066f@quadratum-braccas.com>
References: <328ba050-4a99-d4ea-0f65-6b268c0e8b89@quadratum-braccas.com>
	<CAH2-WzmisQecU9hS5Ht5jqm15uTp4pa7trMxbpSyDEWvMNgKMg@mail.gmail.com>
	<293bf7b3-9fe0-e49e-eaee-031aaf11066f@quadratum-braccas.com>

S Bob <sbob@quadratum-braccas.com> writes:
> On 11/2/20 9:55 AM, Peter Geoghegan wrote:
>> Is signal 10 SIGBUS on your platform? Perhaps check the relevant man
>> page on your platform -- "man signal.7" works for me here.
>> What CPU architecture and operating system are you using?

> 32 bit, Solaris 10

Solaris should be enough like other Unixen to presume that SIGBUS is 10.
However, that doesn't get you far towards finding a root cause.

Since you have a core file, maybe you could extract a stack trace
from it?  We have some suggestions at

https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD

although I'm afraid that's pretty gdb-specific, and Solaris probably
has different debugging tools.

What PG version are you running, exactly?

			regards, tom lane





view thread (6+ messages)  latest in thread

Message-ID: <686892.1604340246@sss.pgh.pa.us>
Permalink:  ../686892.1604340246@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/686892.1604340246@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-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, sbob@quadratum-braccas.com, pg@bowt.ie
  Subject: Re: How to analyze a core dump
  In-Reply-To: <686892.1604340246@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