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.94.2) (envelope-from ) id 1tBcwP-0054PE-QU for pgsql-bugs@arkaria.postgresql.org; Thu, 14 Nov 2024 16:43:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tBcwM-005mb9-R4 for pgsql-bugs@arkaria.postgresql.org; Thu, 14 Nov 2024 16:43:31 +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.94.2) (envelope-from ) id 1tBcwM-005mb1-H5 for pgsql-bugs@lists.postgresql.org; Thu, 14 Nov 2024 16:43:31 +0000 Received: from relay1-d.mail.gandi.net ([2001:4b98:dc4:8::221]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tBcwJ-001vdj-84 for pgsql-bugs@lists.postgresql.org; Thu, 14 Nov 2024 16:43:30 +0000 Received: by mail.gandi.net (Postfix) with ESMTPSA id 7462F240006; Thu, 14 Nov 2024 16:43:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vondra.me; s=gm1; t=1731602604; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=zVh4b+ZhfWFSztXeH9p84XmLq4zjBLp51rhpdnTsQ/E=; b=SV3xJF4PTBVKSPLJzTImtr+vDli2frDHu2l1gpTSLIHtCyqD5jGwbvZYJcOSwx1srLbD3/ VpkdtSwR6vmWV9Qksrwu98HrUAJLVtKnTVppqS64/xdeB+DpdMc/I9IADZKiJTkxQx+iqL kPNFd4trzzEu+PUf3P2N9V/f11bWpatL6xXxAWdjdeBFSg3BZairR8RTkO6srUaiPu7ukU f+ay9T+NoLQ7QDIFv1h4Cxq+XG5gjt2CDnkL8mQP2Z4xmTunyAMv7b3kE6bolL+dSRFNlD 1IUgiNLLtLuqd6gxJziO9gABrHSoISaguj5CYJhbv/vjepAb4g3CXEVQqGBS9w== Message-ID: Date: Thu, 14 Nov 2024 17:43:22 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Regression from postgresql14 to postgresql17 with postgis (osm2pgsql) To: Elie Gedeon , pgsql-bugs@lists.postgresql.org References: Content-Language: en-US From: Tomas Vondra In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-GND-Sasl: tomas@vondra.me List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 11/13/24 20:01, Elie Gedeon wrote: > Hi, > ... > > 2024-11-13 18:15:15 Creating geometry index on table 'planet_osm_line'... > 2024-11-13 18:32:22 Creating osm_id index on table 'planet_osm_line'... > WARNING: page verification failed, calculated checksum 27154 but > expected 30568 > 2024-11-13 18:44:44 Creating geometry index on table 'planet_osm_polygon'... > 2024-11-13 19:18:28 Creating osm_id index on table 'planet_osm_polygon'... > WARNING: page verification failed, calculated checksum 63824 but > expected 53140 > 2024-11-13 19:36:44 Done postprocessing on table 'planet_osm_ways' in > 7358s (2h 2m 38s) > 2024-11-13 19:36:44 Done postprocessing on table 'planet_osm_rels' in > 572s (9m 32s) > 2024-11-13 19:36:44 All postprocessing on table 'planet_osm_point' done > in 1852s (30m 52s). > 2024-11-13 19:36:44 All postprocessing on table 'planet_osm_roads' done > in 1334s (22m 14s). > 2024-11-13 19:36:44 ERROR: Database error: ERROR: invalid page in block > 25652861 of relation base/16385/8057509 > CONTEXT: parallel worker > This suggests you probably have storage issues - notice the 'page verification failed' warnings, complaining about checksum errors. I don't know why osm2pgsql doesn't fail right away, maybe it's not checking the result of that command, or something like that The most likely explanation for PG14 working is that it doesn't have checksums enabled. In which case it may have the same issues, it just doesn't notice that. Are there any suspicious I/O errors in dmesg, or something like that? I don't know which filesystem you use, but maybe try with something that has thorough checksumming (like zfs), or check mount options. regards -- Tomas Vondra