James,
I don’t think that section checks against spatial_ref_sys at all. The issue we ran into before when spatial_ref_sys was checked was when there is say an index that uses a ST_Transform or a function used in a table constraint that relies on spatial_ref_sys. In those cases though I think the error was something like can’t find srid 4326 etc. But the error you have below is that the table public.spatial_ref_sys does not exist or for security reasons it’s not accessible. Which version of PG13 are you upgrading from (include the minor as well) and the PostGIS minor/micro e.g what this returns SELECT postgis_full_version() || ‘ ‘ || version(); From: James Sewell <[email protected]> Sent: Tuesday, February 4, 2025 4:15 PM To: PostGIS Users Discussion <[email protected]>; Bradley Latus <[email protected]> Subject: Re: [postgis-users] [postgis-devel] Upgrade issues This seems to be broken again for pg_upgrade? Upgrading from PG 13 -> 16 and getting the same error as above. ERROR: relation "public.spatial_ref_sys" does not exist This was fixed here: https://github.com/postgis/postgis/blob/master/postgis/gserialized_typmod.c#L150 Could it be the code block added above this since 2019? The issue was PostGIS reading pg_spatial_ref_sys before it's populated in a pg_upgrade. Cheers, James _____ The contents of this email are confidential and may be subject to legal or professional privilege and copyright. No representation is made that this email is free of viruses or other defects. If you have received this communication in error, you may not copy or distribute any part of it or otherwise disclose its contents to anyone. Please advise the sender of your incorrect receipt of this correspondence.
