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 1j7iT8-0001S7-T3 for pgsql-bugs@arkaria.postgresql.org; Fri, 28 Feb 2020 16:26:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1j7iT5-0005Ro-9F for pgsql-bugs@arkaria.postgresql.org; Fri, 28 Feb 2020 16:26:27 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1j7iT4-0005Rg-TV for pgsql-bugs@lists.postgresql.org; Fri, 28 Feb 2020 16:26:27 +0000 Received: from mail-wr1-x441.google.com ([2a00:1450:4864:20::441]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1j7iT1-0000ui-LG for pgsql-bugs@lists.postgresql.org; Fri, 28 Feb 2020 16:26:26 +0000 Received: by mail-wr1-x441.google.com with SMTP id y17so3623009wrn.6 for ; Fri, 28 Feb 2020 08:26:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=gWB1NIHkYmYb/oeiJaggdfdwVvHeuFFhYCk2qmLjhzo=; b=Jn4zB26v5s+gIJaT7i6+zyMcjHSWJcfWnoPEyzkqqrNeWbmL915SXVp2WxC7o+megb jRIGoXVrZvXm1K0Pdoq2E8TLb2GzYFQpyoHzqEKyO1bSYDDK+bwfsQZtg08aM1J9HZnn /0ds39Iu6CLAbSJFsgjHG1E2obY0eoGtOPv99IKm4oiSy0eca1l4fGq9bSwqyuuXiMs7 bLD0lJJqvzmRj6E805ixfP2Ddoa4b1hyYrp29KHG90myTKbVXJC35P5uhnv1mhrhzPRj lJ+6jIA00TOEUdbzdiXFwGh1SQxzoxe3hJF2bAygHOpOCYqDoUoXD+uW2ZLKudrbgBns +e1A== 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:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=gWB1NIHkYmYb/oeiJaggdfdwVvHeuFFhYCk2qmLjhzo=; b=OHjkXa0IuG/NsGt2jeqml6KUHkdy3Ib1/BVvv3GedynoxRWuTfQPR+ZYIqjazaU+QD chj8GZefWI8maxaS9a5JnPjsOQftM5vNG3Kq7GkR/CkYk1h7p4IuOU2PU50I6bcH3tko CBosFqZVv3vWeiu26RjRLX8kfQrNynwiZm5L/jx5Ws1mWFMv8HmjFcJcDwu++g0Sf72A TULnFw6hsWEBBJEn4Z2v07bibtGFRoCMur/VMrk4M316xFCCqNBsWnIP33XKHxf4PU3Z dKksn4NvipEEpdxhq7BMZggLctkm4YPpPVwifYQA1P0fAIZdsPn1opdHF7B0az3vPSik cpoA== X-Gm-Message-State: APjAAAWgyKayYmx45YCqIA6s8Lif10fPA3KVAKN7aASaAq/2D+sCnW9s d/KSRaeHXrrEuzUjqK5IKP3NGQ== X-Google-Smtp-Source: APXvYqz/ZGgw6O2sfRVotdK7cYfaVAJD/4J7bo1N2uVSBiZv0cC8KnZykRoPd1uXm1OB2ikYmrMk6w== X-Received: by 2002:adf:f491:: with SMTP id l17mr5975081wro.149.1582907183006; Fri, 28 Feb 2020 08:26:23 -0800 (PST) Received: from localhost (ip-86-49-253-92.net.upcbroadband.cz. [86.49.253.92]) by smtp.gmail.com with ESMTPSA id j66sm2892583wmb.21.2020.02.28.08.26.21 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 28 Feb 2020 08:26:21 -0800 (PST) Date: Fri, 28 Feb 2020 17:26:20 +0100 From: Tomas Vondra To: przemyslaw.szustak@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16283: crash on create index segmentation fault Message-ID: <20200228162620.pfrugnfk527bml6y@development> References: <16283-89418c2816e96f07@postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <16283-89418c2816e96f07@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Fri, Feb 28, 2020 at 02:23:21PM +0000, PG Bug reporting form wrote: >The following bug has been logged on the website: > >Bug reference: 16283 >Logged by: Przemysław Szustak >Email address: przemyslaw.szustak@gmail.com >PostgreSQL version: 10.12 >Operating system: Ubuntu 16.04.6 LTS >Description: > >Postgresql crash segmentation fault on create index. >More info https://github.com/przemyslaw-szustak/postgresql_postgis_crash. > This seems more like a bug in postgis, considering the last frame before the segfault looks like this: #0 0x000055fb9015c45b in pfree () #1 0x00007f64ee7f2b5e in ?? () from /usr/lib/postgresql/10/lib/postgis-2.5.so #2 0x00007f64ee7f4367 in gserialized_gist_picksplit () from /usr/lib/postgresql/10/lib/postgis-2.5.so #3 0x000055fb9013a272 in FunctionCall2Coll () #4 0x000055fb8fd7f526 in gistSplitByKey () so it's a call from GiST, but the last two calls are somewhere in PostGIS library. If I had to guess, I'd say this looks like double-free or something like that. Which PostGIS version are you using? Are you sure you have the latest 2.5.x version? Also, maybe try to install packages with debug symbols, that should give us a bit more context (parameters, line numbers, ...). regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services