Date: Sun, 17 Feb 2019 16:21:29 -0600
From: Justin Pryzby <pryzby@telsasoft.com>
To: Jakub Glapa <jakub.glapa@gmail.com>
Cc: pgsql-performance@postgresql.org,
	Thomas Munro <thomas.munro@enterprisedb.com>
Subject: Re: dsa_allocate() faliure
Message-ID: <20190217222129.GE28750@telsasoft.com>
References: 
 <CAJk1zg0x881aTwbEM8d-5EWVPfVWxN+Z56+parZ1WFc5DVcgmA@mail.gmail.com>
 <CAJk1zg10iCNsxFvQ4pgKe1B0rdjNG9iELA7AzLXjXnQm5T=KzQ@mail.gmail.com>
 <20181122160958.GJ10913@telsasoft.com>
 <CAJk1zg3nCqG2fo_vg2RwOW6s4TjKnnnqDTrFN4FQMVAT5XEbMQ@mail.gmail.com>
 <20181123161028.GL10913@telsasoft.com>
 <CAJk1zg0pdKJzH6=gDOK52SfLkbNTT=jBkRneCEzDNCEPPBVo6g@mail.gmail.com>
 <CAJk1zg3ZXhDsFg7tQGJ3ZD6N9dp+Q1_DU2N3=s3Ywb-u6Lhc5A@mail.gmail.com>
 <20181126155207.GZ10913@telsasoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20181126155207.GZ10913@telsasoft.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: bulk

Hi,

On Mon, Nov 26, 2018 at 09:52:07AM -0600, Justin Pryzby wrote:
> Hi, thanks for following through.
> 
> On Mon, Nov 26, 2018 at 04:38:35PM +0100, Jakub Glapa wrote:
> > I had a look at dmesg and indeed I see something like:
> > 
> > postgres[30667]: segfault at 0 ip 0000557834264b16 sp 00007ffc2ce1e030
> > error 4 in postgres[557833db7000+6d5000]
> 
> That's useful, I think "at 0" means a null pointer dereferenced.

Thomas fixed several bugs in DSA, which will be in next release, postgres 10.8
and 11.3.

However that doesn't explain the segfault you saw, and I don't see anything
which looks relevant changed since in 10.5.

If you still see that using the latest minor release (10.7), please try to
capture a core file and send a backtrace with a new thread on pgsql-hackers.

Thanks,
Justin