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.98.2) (envelope-from ) id 1xPirF-00000000rTY-3CKT for pgsql-bugs@arkaria.postgresql.org; Sat, 07 Nov 2026 16:01:35 +0000 Received: from localhost ([127.0.0.1]:57122 helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xPirF-000000049lg-3vVo for pgsql-bugs@arkaria.postgresql.org; Sat, 07 Nov 2026 16:01:33 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]:40140) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xPO5i-00000000twO-2b1o for pgsql-bugs@lists.postgresql.org; Fri, 06 Nov 2026 17:51:06 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xPO5f-00000000afr-3Z08 for pgsql-bugs@lists.postgresql.org; Fri, 06 Nov 2026 17:51:05 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=Os4wNqkoVYJ6JOD4qUolYhCfl6XuO6eUn1/e/zmOH1Q=; b=cN8uDV9f9Ano1SV6IQfX2az+Xq kmQO6nUFr6W2YAXO433mPbIVXMKf6z1M1a5XQDdOaR1DDGwByQshCsUDcno/q6CVbRwSv1DlLU5jj jtlKejl19D1OTSogfbB48dU8j/67ilBg/vWg95Tg4u1R/cQvEYj44D39+eP46fmjvvwl+8XqIlFlN adL3Ujf14+ygXAGWygUnIkVvLswZhn8AJBfy3R3fHbxiJcG64v2Bm0Ak1eQiWI6G0bzi7qsU7r0q7 juvpj7rhnjhkJT1kyijPLG/SXoLO6wCjVzRNicfBB42EsZzOPmb3QDb6yG7wCtu6zXTqMz9BWyetS 2FTein/Q==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xPO5g-00000001ba3-04TC for pgsql-bugs@lists.postgresql.org; Fri, 06 Nov 2026 17:51:04 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xPO5e-000000044ZH-3Rxj for pgsql-bugs@lists.postgresql.org; Fri, 06 Nov 2026 17:51:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: BUG #19836: Backend crash with large hash partition modulus To: pgsql-bugs@lists.postgresql.org From: PG Bug reporting form Cc: sumedhpathak@gmail.com Reply-To: sumedhpathak@gmail.com, pgsql-bugs@lists.postgresql.org Date: Fri, 06 Nov 2026 17:50:56 +0000 Message-ID: <19836-0754d466a59c7d00@postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following bug has been logged on the website: Bug reference: 19836 Logged by: Sumedh Pathak Email address: sumedhpathak@gmail.com PostgreSQL version: 19rc1 Operating system: MacOS Description: =20 Hi, The following SQL crashes PostgreSQL 20devel (72b9498df9a, macOS ARM64): CREATE TABLE parent (i integer) PARTITION BY HASH (i); CREATE TABLE p0 PARTITION OF parent FOR VALUES WITH (MODULUS 3, REMAINDER 0); CREATE TABLE p1 PARTITION OF parent FOR VALUES WITH (MODULUS 2147483646, REMAINDER 2); The third statement causes a crash and server recovery. In check_new_partition_bound(), remainder +=3D spec->modulus overflows signed = int (2 + 2147483646), leading to an out-of-bounds lookup. The crash was verified on PG 17,18 as well, but it seems like it exists since PG11. Thanks.