Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1j7k70-0004jl-Cy for pgsql-bugs@arkaria.postgresql.org; Fri, 28 Feb 2020 18:11:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1j7k6y-0007Lg-UU for pgsql-bugs@arkaria.postgresql.org; Fri, 28 Feb 2020 18:11:44 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1j7k6y-0007LZ-DG for pgsql-bugs@lists.postgresql.org; Fri, 28 Feb 2020 18:11:44 +0000 Received: from mail-wm1-x341.google.com ([2a00:1450:4864:20::341]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1j7k6u-0006G6-DU for pgsql-bugs@lists.postgresql.org; Fri, 28 Feb 2020 18:11:42 +0000 Received: by mail-wm1-x341.google.com with SMTP id a5so4198851wmb.0 for ; Fri, 28 Feb 2020 10:11:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=PclSseukbnYjX9rh5RIDWoVeyuCm9z5pIBCR398c2dI=; b=HabIFeKk3nSr58W177YAviJEsM9aThrxUqf34u4SRJjuZFhmuGEL3TCfSPUJOYCdi/ ea/JHUMBJnmLqcvxK/8Q+dFS7MuYUZeLL61B9SfGcqeFjfTYGLky/Z/3GY2S/Q5TUtCM UFuXe700K0iyGIldFjgWFrhE85T4IYhvENFLtfI1NYawf6urqUGHoAVTK71nZ5ljZ9bF Q18QOJGQePr74ZF//XNQYM/zNjYxBGVStc/Xeg4RwA3mZqTyuMSmO+NeDOfuBb4Xild8 dnTObkvqRHLBoPFoHqgDmNmy/VSdEnN10qu+mrZY1m58ca8oaSGzIBawjHWyZxbFsaK4 30Fg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=PclSseukbnYjX9rh5RIDWoVeyuCm9z5pIBCR398c2dI=; b=m7Es5dS1SgB5g7svEzY7rdJ6ko9c0c5eNLhRMg2W9Wt7r1W5Xm2QHENy7ZqIsJdPq3 DAqgvxFKbpR4dXznuDanibKCmDA/xILwUmE97iT0syCHPqLmtfjaoI9AZhEQ3wdgBmQ2 n1KPp+n0P7mZckSXQ4Q5U68jcD4OZjISZ7aMXO4/a5nCXdOOFbV5f+qvqJY8l5BlhMOk YBxCg3cPWB/BirEkALKZtoVVeGcgE0XFGsEn3TsTkxa0cYuq4B7BFUKMbAMDJBsNl9hL 2LBw16iR0epSQr/nruXPfcCHSE2+rAl40qu5qtJNWi+VztOemawsRsRzLmaUMaLRhXLO tMjA== X-Gm-Message-State: APjAAAXosHK3TzckhF2qeHnOn2LOKBLYIgApg5SE4e0Ve9kLwgXLgEiW UT9sEYFfPpABBqu9OcBh9S+1Ew== X-Google-Smtp-Source: APXvYqym7CAIJQuoH+RiOgOZwCpG/eJ3nnT8Q5BpK6WnwUP6xTJoSA3uBvq0ziWevlJp0Sr2DP1Wnw== X-Received: by 2002:a1c:156:: with SMTP id 83mr6112679wmb.151.1582913497460; Fri, 28 Feb 2020 10:11:37 -0800 (PST) Received: from localhost (ip-86-49-253-92.net.upcbroadband.cz. [86.49.253.92]) by smtp.gmail.com with ESMTPSA id v8sm13157846wrw.2.2020.02.28.10.11.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 28 Feb 2020 10:11:36 -0800 (PST) Date: Fri, 28 Feb 2020 19:11:35 +0100 From: Tomas Vondra To: =?utf-8?Q?Przemys=C5=82aw?= Szustak Cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16283: crash on create index segmentation fault Message-ID: <20200228181135.hkbtwdlvxfv37khn@development> References: <16283-89418c2816e96f07@postgresql.org> <20200228162620.pfrugnfk527bml6y@development> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Fri, Feb 28, 2020 at 06:43:40PM +0100, Przemysław Szustak wrote: >I don't know why but now when I created this howto recreate crash I used >new cluster (on these same server) and now system crash file is not created. >So now I have only info that postgres process has Segmentation fault. > You probably need to tweak kernel.core_pattern - some systems have custom scripts to process core files etc. >I think that problem is in >https://github.com/postgis/postgis/blob/master/postgis/gserialized_gist_nd.c#L1378. > >I have had latest postgis from ubuntu apt update (POSTGIS="2.5.3 r17699" >[EXTENSION] PGSQL="100" GEOS="3.7.1-CAPI-1.11.1 27a5e771" PROJ="Rel. 4.9.2, >08 September 2015" GDAL="GDAL 1.11.3, released 2015/09/16" LIBXML="2.9.3" >LIBJSON="0.11.99" LIBPROTOBUF="1.2.1" RASTER). > Yeah, that seems like the most recent version. >So maybe I should report it to postgis bug tracking system? > Maybe, but I guess they'll ask you for the same information. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services