Re: Regression from postgresql14 to postgresql17 with postgis (osm2pgsql)

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