Re: gharial segfaulting on REL_12_STABLE only

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: gharial segfaulting on REL_12_STABLE only
Date: 2019-08-29 01:06:32
Message-ID: CA+hUKG+Cj8TtXN4_smpWPhc=UPss5cEzAjZNw8VqxXzyDpvrMw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 27, 2019 at 2:09 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> On Tue, Aug 27, 2019 at 1:48 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > A stack trace would likely be really useful right about now.
>
> Yeah. Looking into how to get that.

Erm. I heard the system was in a very unhappy state and couldn't be
logged into. After it was rebooted, the problem appears to have gone
away. That is quite unsatisfying.

"anole" runs on the same host, and occasionally fails to launch any
parallel workers, and it seems to be pretty unhappy too -- very long
runtimes (minutes where my smaller machines take seconds). So the
machine may be massively overloaded and swapping or something like
that, something to be looked into, but that doesn't explain how we get
to a segfault without an underlying hard to reach bug in our code...

--
Thomas Munro
https://enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message movead.li@highgo.ca 2019-08-29 01:14:49 Re: Re: Email to hackers for test coverage
Previous Message Michael Paquier 2019-08-29 00:46:39 Re: Improve error detections in TAP tests by spreading safe_psql