<div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> Paul – any thoughts on how to fix this one?<br>
<br>
None. Is it easily replicable? Does any non-standard geography srid trigger it?<br></blockquote></div></div></blockquote><div><br></div><div>Making some progress now.</div><div><br></div><div>It looks like pg_upgrade from any (tested 9.6, 10, -> 11) version of Postgres will fail if any version of PostGIS (tested 2.5.1, 3.0) is installed and a table with a Geography, non 4326 SRID column exists.</div><div><br></div><div>The failure can take one of two forms:</div><div>a) When the table is created spatial_ref_sys doesn't exist</div><div>b) When the table is created spatial_ref_sys exists but is empty (data isn't added till after the schema import using pg_upgrade)</div><div><br></div><div><br></div><div> I can't answer is how this has not been hit before???</div></div>
</div>
<br>
<hr style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:14.5455px;line-height:normal"><font size="1" color="Gray" face="Arial" style="line-height:normal">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.</font>