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.89) (envelope-from ) id 1ifYdD-0004tm-Ax for pgsql-bugs@arkaria.postgresql.org; Fri, 13 Dec 2019 00:16: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 1ifYdC-0001Nz-0m for pgsql-bugs@arkaria.postgresql.org; Fri, 13 Dec 2019 00:16:30 +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 1ifYdB-0001Me-N9 for pgsql-bugs@lists.postgresql.org; Fri, 13 Dec 2019 00:16:29 +0000 Received: from mail-wm1-x343.google.com ([2a00:1450:4864:20::343]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ifYd8-0003lw-ST for pgsql-bugs@lists.postgresql.org; Fri, 13 Dec 2019 00:16:29 +0000 Received: by mail-wm1-x343.google.com with SMTP id p9so4342513wmc.2 for ; Thu, 12 Dec 2019 16:16: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:in-reply-to; bh=Kccidj8iYgnc67OA6Olz8xnmlvtQYwhwLDKY/UW+1CE=; b=a57goFEXkTEHTWQ3nVF7hb0WCLXeXKThhz28O0Dr8E8nImACBAdL0nvqkaigjlKkmH FdkFfHIu/jUlN3ICpRd/W7mCPV0YaoU0Y6JxkwVni35/5o5Mity/QQVwhvn5PP8vf2wf lqGMNpVDV8Xy9Q12K1rGHyDZJ6lTNmD8OSWLC7aARej605LAdu3iCjPORpJEqOI+BWIG LRKbSvH5qKufQ1sgwjfWASGE9wPG8JGqb0YFsg4w0qUKWxO0B1kAsrp0SBkoeKXW42ci sYRjOncNrGf/l9rsjq6KXY1XpE5a5UqJxyAinAKSGB0sZ+fGz2mFt3eFoBqzLONvDmc0 GRbw== 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:in-reply-to; bh=Kccidj8iYgnc67OA6Olz8xnmlvtQYwhwLDKY/UW+1CE=; b=UB+X1QE37zySNcprBLuTkOjZQx+BME6IkPJTi58NmZ+cnI6qK6i7p00XDJ+dpAGIYr W404PBwZZRsb7Ab09uQpaf7yYE49DNojU9vbvA+ZGJGkYOJ6UIIFNeKN9MJzCVSLC+au kuSOyg7ELuFVoFwTCeWUAAbmn2spOpdNfh0Gvd3oihBkOHnBW1E2vrSZm7hhb7+/OMD8 bMJ2kU4zo7krKjKwK+x0Cd5bdq2O3Ex+XanU8IgMhXOXHZJTjpaIw1jtDp1U6Rapcbzk okcuRNDVmfW0ROPI1PwXlVxJ4gfi0ZC2Jt/EvRh8eELCsn25MMn3VqOrxe1+YnRursXr ddxw== X-Gm-Message-State: APjAAAXIs6bdGCelrkzX1u0K5tSnWn3Ow3w9sV7pHhMgHKcdMJfUkGmN IbXN/y3qmd3bSdSgQXzThyBZ4A== X-Google-Smtp-Source: APXvYqzgVB36WatzZ9UuCBNqiGgAMCOcbJ/q48idJ8Jw/tF3OC6KYqeQEPmbvkFrznmhSiYBLMeFCQ== X-Received: by 2002:a05:600c:108a:: with SMTP id e10mr9310141wmd.38.1576196185475; Thu, 12 Dec 2019 16:16:25 -0800 (PST) Received: from localhost (ip-86-49-253-92.net.upcbroadband.cz. [86.49.253.92]) by smtp.gmail.com with ESMTPSA id k13sm8106848wrx.59.2019.12.12.16.16.20 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 12 Dec 2019 16:16:20 -0800 (PST) Date: Fri, 13 Dec 2019 01:16:18 +0100 From: Tomas Vondra To: Jeff Janes Cc: Tom Lane , kunert@cms.hu-berlin.de, pgsql-bugs Subject: Re: BUG #16162: create index using gist_trgm_ops leads to panic Message-ID: <20191213001618.jqeousv77xnlds7x@development> References: <16162-45d21b7b6c1a3105@postgresql.org> <20191212125023.vpk6zbbeldzmyerc@development> <26141.1576158262@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Thu, Dec 12, 2019 at 07:05:53PM -0500, Jeff Janes wrote: >On Thu, Dec 12, 2019 at 8:44 AM Tom Lane wrote: > >> >> I wonder if this could be a recently-introduced bug? I do not >> recall seeing complaints like this before v12. >> > >Looks like the culprit is: > >commit 9155580fd5fc2a0cbb23376dfca7cd21f59c2c7b >Author: Heikki Linnakangas >Date: Wed Apr 3 17:03:15 2019 +0300 > > Generate less WAL during GiST, GIN and SP-GiST index build. > >The commit before went 150 iterations with no failures, while this one >failed on the 15th iteration, then again on 4th. > Thanks for the bisect. I've planned to try reproducing this on 11, but this commit only in 12, so Tom is right it's a recent bug. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services