From: | Victor Wagner <vitus(at)wagner(dot)pp(dot)ru> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: make check crashes on POWER8 machine |
Date: | 2020-03-13 13:16:10 |
Message-ID: | 20200313161610.0af5ed9a@fafnir.l.postgrespro.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 13 Mar 2020 07:43:59 -0500
Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> On Fri, Mar 13, 2020 at 10:29:13AM +0300, Victor Wagner wrote:
> > Hi,
> >
> > I've encountered a problem with Postgres on PowerPC machine.
> > Sometimes
>
> Is it related to
> https://www.postgresql.org/message-id/20032.1570808731%40sss.pgh.pa.us
> https://bugzilla.kernel.org/show_bug.cgi?id=205183
I don't think so. At least I cannot see any signal handler-related stuff
in the trace, but see lots of calls to stored procedure executor
instead.
Although several different stack traces show completely different parts
of code when signal SIGSEGV arrives, which may point to asynchronous
nature of the problem.
Unfortunately I've not kept all the cores I've seen.
It rather looks like that in some rare circumstances Postgres is unable
to properly determine end of stack condition.
--
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2020-03-13 13:21:14 | Re: [proposal] de-TOAST'ing using a iterator |
Previous Message | Justin Pryzby | 2020-03-13 13:12:32 | Re: pg_ls_tmpdir to show directories and shared filesets (and pg_ls_*) |