Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w2qfF-000f9w-02 for pgsql-bugs@arkaria.postgresql.org; Wed, 18 Mar 2026 13:10:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w2qfD-00AmVL-2Y for pgsql-bugs@arkaria.postgresql.org; Wed, 18 Mar 2026 13:10:19 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w2qfD-00AmVA-1Z for pgsql-bugs@lists.postgresql.org; Wed, 18 Mar 2026 13:10:19 +0000 Received: from udcm-wwu2.uni-muenster.de ([128.176.118.28]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1w2qf9-00000000MOh-15GY for pgsql-bugs@lists.postgresql.org; Wed, 18 Mar 2026 13:10:18 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uni-muenster.de; i=@uni-muenster.de; q=dns/txt; s=uniout; t=1773839417; x=1805375417; h=message-id:date:mime-version:subject:to:references:from: in-reply-to:content-transfer-encoding; bh=+szNIdKxYGIAXKGL31yiDLuBppWTAj+gHKTTMUqmxrE=; b=fV3djw/hTwguOMJLGZhS2SZxjywCRbCPI6G8lGfnFTa0QtChtiqaFcP6 ISLyboUUlWo5IKhQY6N0B+v6oQtloIkg6WS4GBjMsDG/Xj2pLqbjB2f9M SKJhp7xBEWH9EyU731m3t19fqnQ6ANvkJW7oCXpVzLAlsTY4MqB8RFzhZ jP/0V26ThNz4CHzwSND8AgpdYk2Jn7fNLEtUKnux7rTIbDBLc2e9e20qb iIpXdJpV1XLADrS9fhvbfMFbuxjKSomKCr342J68pyx+WVEwx8sGMmKkm aJXewtcS92JxXrNuXFBTN4OqoM0AT1/c+geaM0Uo57/DsQ36tGwIJHwgi w==; X-CSE-ConnectionGUID: 6sfl/HbAS3WGNdRUiQLVOw== X-CSE-MsgGUID: cTdPFTxFQqGldHlnht3Mmw== X-IronPort-AV: E=Sophos;i="6.23,127,1770591600"; d="scan'208";a="388079678" Received: from secmail.uni-muenster.de ([128.176.118.4]) by UDCM-RELAY2.UNI-MUENSTER.DE with ESMTP; 18 Mar 2026 14:10:14 +0100 Received: from [192.168.178.27] (dynamic-093-131-014-046.93.131.pool.telefonica.de [93.131.14.46]) by SECMAIL.UNI-MUENSTER.DE (Postfix) with ESMTPSA id 13EF920ADF00; Wed, 18 Mar 2026 14:10:12 +0100 (CET) Message-ID: <941c71e4-3b46-4eab-a5de-b59511ab1018@uni-muenster.de> Date: Wed, 18 Mar 2026 14:10:12 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Segmentation fault in PostgreSQL 17.7 during REINDEX TABLE CONCURRENTLY To: Ana Almeida , "pgsql-bugs@lists.postgresql.org" References: Content-Language: de-DE, en-GB From: Jim Jones In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi Ana On 18/03/2026 10:54, Ana Almeida wrote: > 2026-03-17 18:19:55.244 WAT [2261667] LOG:  server process (PID 2382873) > was terminated by signal 11: Segmentation fault > > 2026-03-17 18:19:55.244 WAT [2261667] DETAIL:  Failed process was > running: REINDEX TABLE CONCURRENTLY sibs.purchases; > > 2026-03-17 18:19:55.244 WAT [2261667] LOG:  terminating any other active > server processes > > 2026-03-17 18:19:55.257 WAT [2261667] LOG:  all server processes > terminated; reinitializing > > 2026-03-17 18:19:55.354 WAT [2382972] LOG:  database system was > interrupted; last known up at 2026-03-17 18:18:58 WAT > > 2026-03-17 18:19:55.449 WAT [2382972] LOG:  database system was not > properly shut down; automatic recovery in progress > > 2026-03-17 18:19:55.457 WAT [2382972] LOG:  redo starts at 310/8142BEC0 > > 2026-03-17 18:19:56.352 WAT [2382972] LOG:  invalid record length at > 310/988BAA18: expected at least 24, got 0 > > 2026-03-17 18:19:56.352 WAT [2382972] LOG:  redo done at 310/988BA9E0 > system usage: CPU: user: 0.28 s, system: 0.34 s, elapsed: 0.89 s > > 2026-03-17 18:19:56.360 WAT [2382973] LOG:  checkpoint starting: end-of- > recovery immediate wait I was unable to reproduce the bug. Could you share a bit more data on the table and indexes that caused the system crash? Best, Jim