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 1wYoIz-000WPy-2d for pgsql-bugs@arkaria.postgresql.org; Sun, 14 Jun 2026 17:07:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wYoIw-008dMu-0p for pgsql-bugs@arkaria.postgresql.org; Sun, 14 Jun 2026 17:07:26 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wYepK-005o8M-0j for pgsql-bugs@lists.postgresql.org; Sun, 14 Jun 2026 07:00:14 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wYepC-00000000J9R-1ntO for pgsql-bugs@lists.postgresql.org; Sun, 14 Jun 2026 07:00:08 +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=mb+xp8i34YavDq/A2CaCIIaFWCQqd4/JRvM5MgYDvn0=; b=cQaZDPPFlgHG4th2z1k1qOmwpv FSt8ZcEqnBCdqVgDDCBUnDPiSd9zwXVloSXzWhC3T+yPGYAD1tqk+WnxkpXLEzgqEcyNQNjRn2pdW HT7nb9C5e0NFRHPOHtqpkxJYgpcOZEkfUPHRdXfnDBrXxWwefYUCz/EEohXazyjjdsw/6POA9tm5p 97F8f3Gx5YdFHV0jQfbGVpNpBNomMxNJV9oArDT6+pCigukBKNYDeVqxNYNOTgS08Mno4eIG2UhMZ iufnAFxB6SerAOZCMadNXhH5X2uTB4uBMX+XqGPAJNDSKHEewGoWLmndX5r0VBfo/BjY8kPIIyTbm 9JpHiHgA==; 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.96) (envelope-from ) id 1wYepA-000sJo-1F for pgsql-bugs@lists.postgresql.org; Sun, 14 Jun 2026 07:00:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wYep9-001jcG-1W for pgsql-bugs@lists.postgresql.org; Sun, 14 Jun 2026 07:00:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: BUG #19519: REPACK can fail due to missing chunk for toast value To: pgsql-bugs@lists.postgresql.org From: PG Bug reporting form Cc: exclusion@gmail.com Reply-To: exclusion@gmail.com, pgsql-bugs@lists.postgresql.org Date: Sun, 14 Jun 2026 07:00:01 +0000 Message-ID: <19519-fe02d8ff679d834d@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: 19519 Logged by: Alexander Lakhin Email address: exclusion@gmail.com PostgreSQL version: 19beta1 Operating system: Ubuntu 24.04 Description: =20 The following script: createdb db1 createdb db2 cat << EOF | psql db1 SET default_statistics_target =3D 1000; CREATE TABLE t(i int, t text); INSERT INTO t SELECT 1, g::text FROM generate_series(1, 50000) g; ANALYZE t; EOF cat << EOF | psql db2 & BEGIN; CREATE TABLE t(i int); SELECT pg_sleep(3); EOF sleep 1 cat << EOF | psql db1 DROP TABLE t; VACUUM pg_toast.pg_toast_2619; REPACK; EOF wait triggers: ERROR: missing chunk number 0 for toast value 16393 in pg_toast_2619 Reproduced starting from ac58465e0.