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 1j7mkO-00038z-Rn for pgsql-bugs@arkaria.postgresql.org; Fri, 28 Feb 2020 21:00:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1j7mkM-00085Y-IH for pgsql-bugs@arkaria.postgresql.org; Fri, 28 Feb 2020 21:00:34 +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 1j7mkM-00085R-2h for pgsql-bugs@lists.postgresql.org; Fri, 28 Feb 2020 21:00:34 +0000 Received: from mail-wr1-x444.google.com ([2a00:1450:4864:20::444]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1j7mkE-0007XD-G5 for pgsql-bugs@lists.postgresql.org; Fri, 28 Feb 2020 21:00:32 +0000 Received: by mail-wr1-x444.google.com with SMTP id m16so4561868wrx.11 for ; Fri, 28 Feb 2020 13:00:26 -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=1+yIISzmL4ueQqG5w2w/rkUGueWplJ8s7u5v+Mg1M+s=; b=YMibEEasrhqav9fZeNy81PNV3h4g58QSmf3sQioQvFkTecvUsuwoMHQBjwKAVM/DU8 t25042a3RX6jsvb4CYZLxfPE8sWsdFeYLAajycH9SNjP/gRWgcqSgTcbi4CPmQXA82Wr FUYEN0aEbe/3nyGuVZ6f0981PsDZb7mQzkMkKStallS3Cs9pRdesJnbWqyG6SN2+H+1r ywoFYLVQRXAVJn2bjFWU4V2X3iBf+YDTvZ+i4kNQlKKlNlTLH58RwGWJW9MeJpBiqaUH l/nDnQ5HTMgPJ+ksnhpAInO2wnidJ1zi5iwm53vBDRnlsgdCIK5mT5iB5DLzRaBJH8V7 hEzw== 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=1+yIISzmL4ueQqG5w2w/rkUGueWplJ8s7u5v+Mg1M+s=; b=SPnBJ6y53119Y+GAJN/wNdYxW1R/z87sfMua+E78F1g/BptHIFRa8jxfG6+1nenf+n RsxV9wc46fN7HhwEPZumKl5hJCxTLew8TLTQidSYsAig1fksy4baD8I3Pemjg58b7vSN l2CYHJ1MPDnHW0eteyAaujs/9D+htDg4Mty2VyHDEKSA5vLZfxEQWC6IEw13Cy8sVgCc pc6AGfsA7ASZW0pkSCQeTGPnbud1B5Iu7+vQNgmi0uOb/AVwhEIa7QAad1dWWYbhfwhS CztplEQ9VQjJ0IAIZuttqlpwL5p1D1Hi+sBC4aVWxOjSFD9mIz7EYvYxy5FCIY4aX6f9 CGJQ== X-Gm-Message-State: APjAAAV/lzY68fAATODbP3MhuTMownbK6FlUzxLAjSFnhwsJ53OGKZt2 QjApp5uatEVtud6jttz3/68YIQ== X-Google-Smtp-Source: APXvYqw6fJGnfi6VzgQMExn5u0cCh1BItxE+vrwrxiyqBZxgssc1cAgF7OWCQjRO1yXrPXKVBjJOaQ== X-Received: by 2002:a5d:4692:: with SMTP id u18mr6505977wrq.206.1582923623703; Fri, 28 Feb 2020 13:00: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 w1sm3750438wmc.11.2020.02.28.13.00.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 28 Feb 2020 13:00:22 -0800 (PST) Date: Fri, 28 Feb 2020 22:00:21 +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: <20200228210021.znum3xr3kprj3qec@development> References: <16283-89418c2816e96f07@postgresql.org> <20200228162620.pfrugnfk527bml6y@development> <20200228181135.hkbtwdlvxfv37khn@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 08:58:19PM +0100, Przemysław Szustak wrote: >I updated info on github logs because now system was generated new core >dump. > >How can I get you more information? I don't now how to debug it. > Well, it's hard to say what exactly is happening, without getting a better backtrace. Your system is apparently missing debug symbols, so you need to do something like sudo aptitude install postgresql-10-dbg or something like that. And the same for postgis, I assume. Then generate the backtrace again (using the existing core file). You might also attach gdb to the running backend, trigger the issue and do more investigation there. 1) determine the PID of the backend handling your connection db=# select pg_backend_pid(); 2) attach GDB to the process $ gdb -p $PID (gdb) c 3) Run the query using the same backend, once it triggers you'll be able to do 'bt' in the gdb shell and inspect variables. This needs the debug symbols too, though. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services