From: Tom Lane <tgl@sss.pgh.pa.us>
To: S Bob <sbob@quadratum-braccas.com>
cc: Peter Geoghegan <pg@bowt.ie>, pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: How to analyze a core dump
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>
Comments: In-reply-to S Bob <sbob@quadratum-braccas.com>
	message dated "Mon, 02 Nov 2020 10:04:28 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <686891.1604340246.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 02 Nov 2020 13:04:06 -0500
Message-ID: <686892.1604340246@sss.pgh.pa.us>
Precedence: bulk

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_Postgr=
eSQL_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