Re: [sqlsmith] crash in RestoreLibraryState during low-memory testing

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Andreas Seltenreich <seltenreich(at)gmx(dot)de>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [sqlsmith] crash in RestoreLibraryState during low-memory testing
Date: 2017-10-03 03:01:44
Message-ID: CAA4eK1JtFh7uZHD5O6n2onhw=+5q0maOCbUGPaGtcG2bNeRN=g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 3, 2017 at 3:04 AM, Andreas Seltenreich <seltenreich(at)gmx(dot)de> wrote:
> Hi,
>
> doing low-memory testing with REL_10_STABLE at 1f19550a87 also produced
> a couple of parallel worker core dumps with the backtrace below.
> Although most of the backtrace is inside the dynamic linker, it looks
> like it was passed a pointer to gone-away shared memory.
>

It appears to be some dangling pointer, but not sure how it is
possible. Can you provide some more details, like do you have any
other library which you want to get loaded in the backend (like by
using shared_preload_libraries or by some other way)? I think without
that we shouldn't try to load anything in the parallel worker. Also,
if you can get the failed query (check in server log), it would be
great.

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-10-03 03:06:09 Re: Horrible CREATE DATABASE Performance in High Sierra
Previous Message Michael Paquier 2017-10-03 02:48:43 Re: [PATCH] Tests for reloptions