<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Aptos;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.xmsonormal, li.xmsonormal, div.xmsonormal
{mso-style-name:x_msonormal;
margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:281812248;
mso-list-template-ids:-1748236648;}
@list l0:level1
{mso-level-start-at:4;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:326640938;
mso-list-template-ids:253110458;}
@list l2
{mso-list-id:568072872;
mso-list-template-ids:-1756198682;}
@list l2:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3
{mso-list-id:569925404;
mso-list-template-ids:-330132438;}
@list l3:level1
{mso-level-start-at:5;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4
{mso-list-id:1068921105;
mso-list-template-ids:-285409486;}
@list l4:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5
{mso-list-id:1800144575;
mso-list-template-ids:26618428;}
@list l5:level1
{mso-level-start-at:6;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt'>Yah dropping the raster extension if you are not using it would be my first suggestion.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>If you do <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>DROP EXTENSION postgis_raster;<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>And it successfully drops, then you definitely don’t have data tied to it so safe to drop before you do your pg_dump and restore.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>I’ve seen people complain about random crashes with for example a bad netcdf driver that gets loaded when gdal lib is loaded. So if you are running into one of those types of issues, not installing the raster extension will save you from that pain.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>I do see you have Azure postgis compiled with GEOS 3.10.2, but you are running with 3.11.1. In theory that shouldn’t be an issue since 3.10.2 is upward compatible with 3.11.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Everything else at a glance looks to be in shape.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Hope that helps,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Regina<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Jeffrey Durrence <jeffrey.durrence@mcleanengineering.com> <br><b>Sent:</b> Tuesday, April 23, 2024 1:21 PM<br><b>To:</b> Regina Obe <lr@pcorp.us>; postgis-users@lists.osgeo.org<br><b>Subject:</b> Re: Segmentation fault restoring data to Azure VM<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span style='color:black'>Regina,<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>Thank you so much for your quick response (and for your contributions to the rest of us in your writings)!<br><br>On the physical server I have:<br> POSTGIS="3.4.2 c19ce56" [EXTENSION] PGSQL="150" GEOS="3.10.2-CAPI-1.16.0" PROJ="8.2.1 NETWORK_ENABLED=OFF URL_ENDPOINT=https://cdn.proj.org USER_WRITABLE_DIRECTORY=/tmp/proj DATABASE_PATH=/usr/share/proj/proj.db" GDAL="GDAL 3.4.3, released 2022/04/22" LIBXML="2.9.13" LIBJSON="0.15" LIBPROTOBUF="1.3.3" WAGYU="0.5.0 (Internal)" (core procs from "3.4.1 ca035b9" need upgrade) RASTER (raster procs from "3.4.1 ca035b9" need upgrade)<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='color:black'>On the Azure server I have <br>POSTGIS="3.4.2 c19ce56" [EXTENSION] PGSQL="150" GEOS="3.11.1-CAPI-1.17.1" (compiled against GEOS 3.10.2) PROJ="8.2.1 NETWORK_ENABLED=OFF URL_ENDPOINT=https://cdn.proj.org USER_WRITABLE_DIRECTORY=/tmp/proj DATABASE_PATH=/usr/share/proj/proj.db" GDAL="GDAL 3.4.3, released 2022/04/22" LIBXML="2.9.13" LIBJSON="0.15" LIBPROTOBUF="1.3.3" WAGYU="0.5.0 (Internal)" RASTER<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>There are some differences, though I'm not sure of the best strategy to reconcile this. As for the raster extension, I don't use it for my workflows. I could drop the postgis_raster extension and see if that allows my export/import to succeed without error.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>-Jeffrey<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p></div><div id=Signature><p><span style='font-family:"Segoe UI",sans-serif;color:black'>Jeffrey Durrence</span><o:p></o:p></p><p><span style='font-family:"Segoe UI",sans-serif;color:black'>McLean Engineering Company</span><o:p></o:p></p><p><span style='font-family:"Segoe UI",sans-serif;color:black'><a href="http://www.mcleanengineering.com/">www.mcleanengineering.com</a></span><o:p></o:p></p><p><span style='font-family:"Segoe UI",sans-serif;color:black'>Office: 229-985-1148</span><o:p></o:p></p><p><span style='font-family:"Segoe UI",sans-serif;color:black;background:white'>Mobile: 229-798-0480</span><o:p></o:p></p><p> <o:p></o:p></p></div><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="98%" align=center></div><div id=divRplyFwdMsg><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'> Regina Obe <<a href="mailto:lr@pcorp.us">lr@pcorp.us</a>><br><b>Sent:</b> Tuesday, April 23, 2024 1:09 PM<br><b>To:</b> Jeffrey Durrence <<a href="mailto:jeffrey.durrence@mcleanengineering.com">jeffrey.durrence@mcleanengineering.com</a>>; <a href="mailto:postgis-users@lists.osgeo.org">postgis-users@lists.osgeo.org</a> <<a href="mailto:postgis-users@lists.osgeo.org">postgis-users@lists.osgeo.org</a>><br><b>Subject:</b> RE: Segmentation fault restoring data to Azure VM</span> <o:p></o:p></p><div><p class=MsoNormal> <o:p></o:p></p></div></div><div><div><p class=xmsonormal><span style='font-size:11.0pt'>What does </span><o:p></o:p></p><p class=xmsonormal><span style='font-size:11.0pt'> </span><o:p></o:p></p><p class=xmsonormal><span style='font-size:11.0pt'>SELECT postgis_full_version(); </span><o:p></o:p></p><p class=xmsonormal><span style='font-size:11.0pt'> </span><o:p></o:p></p><p class=xmsonormal><span style='font-size:11.0pt'>Run on your current setup vs. your Azure VM setup.</span><o:p></o:p></p><p class=xmsonormal><span style='font-size:11.0pt'> </span><o:p></o:p></p><p class=xmsonormal><span style='font-size:11.0pt'>Might thinking is it might be a dependent library crashing.</span><o:p></o:p></p><p class=xmsonormal><span style='font-size:11.0pt'> </span><o:p></o:p></p><p class=xmsonormal><span style='font-size:11.0pt'>Usually the issues are with postgis_raster extension since that drags in GDAL which drags in several more libraries.</span><o:p></o:p></p><p class=xmsonormal><span style='font-size:11.0pt'> </span><o:p></o:p></p><p class=xmsonormal><span style='font-size:11.0pt'>Could also be an issue with PROJ. As I recall at least on windows, I used to get crashes if PROJ_LIB path wasn’t set, but I think that issue has gone away with recent releases.</span><o:p></o:p></p><p class=xmsonormal><span style='font-size:11.0pt'> </span><o:p></o:p></p><p class=xmsonormal><span style='font-size:11.0pt'>Not sure if it was ever an issue on Linux or Unix.</span><o:p></o:p></p><p class=xmsonormal><span style='font-size:11.0pt'> </span><o:p></o:p></p><p class=xmsonormal><span style='font-size:11.0pt'>Hope that helps,</span><o:p></o:p></p><p class=xmsonormal><span style='font-size:11.0pt'>Regina</span><o:p></o:p></p><p class=xmsonormal><span style='font-size:11.0pt'> </span><o:p></o:p></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=xmsonormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Jeffrey Durrence <<a href="mailto:jeffrey.durrence@mcleanengineering.com">jeffrey.durrence@mcleanengineering.com</a>> <br><b>Sent:</b> Tuesday, April 23, 2024 11:42 AM<br><b>To:</b> <a href="mailto:postgis-users@lists.osgeo.org">postgis-users@lists.osgeo.org</a><br><b>Subject:</b> Segmentation fault restoring data to Azure VM</span><o:p></o:p></p></div></div><p class=xmsonormal> <o:p></o:p></p><div><p class=xmsonormal><span style='color:black'>Greetings,</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'> </span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>I am migrating PostgreSQL/PostGIS databases from a physical server with these specs:<br>Host OS: Ubuntu 22.04.4 LTS x64 (32GB RAM, 8GB Swap, 1TB disk space, XEON E5-1660 CPU)<br>Postgres: 15.6.1-pgdg22.04+1<br>PostGIS: 3.4.2</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'> </span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>To an Azure VM with </span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>Host OS: Ubuntu 22.04.4 LTS x64 (32GB RAM, 8GB Swap, 512GB disk space, XEON 8171M) (again, this is in Azure VM)<br>Postgres: 15.6.1-pgdg22.04+1<br>PostGIS: 3.4.2</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'> </span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'> </span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>In the past, I have migrated the same data from on the same physical hardware for changes in host O/S, Postgres version, and/or PostGIS version. I've also migrated from one physical host to another. When doing so, I try to make sure that my software packages are up to date and that the packages in the destination environment match. I did this for this planned environment as well. Because I know that some of my dbs have several years of history in them, I export these dbs individually using pg_dump (using the custom format when possible but in some cases I use the plain text option) and pg_restore on the destination host.</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'> </span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>During the process of migrating data in this manner, I observed that restoration of many of my dbs failed. I did lots of testing with this and have made these additional observations:</span><o:p></o:p></p></div><div><ol style='margin-top:0in' start=1 type=1><li class=xmsonormal style='color:black;mso-list:l1 level1 lfo1;list-style-type:"1. "'>I am able to restore my export files to another physical host with the same software environment without error. (the errors occur when importing to virtual environment).<o:p></o:p></li></ol></div><div><ol style='margin-top:0in' start=2 type=1><li class=xmsonormal style='color:black;mso-list:l4 level1 lfo2;list-style-type:"2. "'>If I split my export/import into separate steps for the schema and data, it is the schema import that produces the error, not the data import.<o:p></o:p></li></ol></div><div><ol style='margin-top:0in' start=3 type=1><li class=xmsonormal style='color:black;mso-list:l2 level1 lfo3;list-style-type:"3. "'>When the error occurs, the db process terminates with a segmentation vault (see log output below), and the db process restarts.<o:p></o:p></li></ol></div><div><ol style='margin-top:0in' start=4 type=1><li class=xmsonormal style='color:black;mso-list:l0 level1 lfo4;list-style-type:"4. "'>With logging of all statements enabled, I can see that the segmentation vault occurs at the absolute end of the import, when it seems that all commands are completed. So long as I wait on the server process to recover, I have no errors when I import the data following the error.<o:p></o:p></li></ol></div><div><ol style='margin-top:0in' start=5 type=1><li class=xmsonormal style='color:black;mso-list:l3 level1 lfo5;list-style-type:"5. "'>The db imports that produce these errors seem to be those with more history (e.g., it's more likely that these were created with an older version of postGIS and subsequently upgraded to the versions they have now). <o:p></o:p></li></ol></div><div><ol style='margin-top:0in' start=6 type=1><li class=xmsonormal style='color:black;mso-list:l5 level1 lfo6;list-style-type:"6. "'>The errors do seem related to the installation of the PostGIS extension. If I purposely drop the extension from the source database before I export, the resulting file can be imported in the target environment without error. This is obviously undesirable as it results in my losing all of the geometry info from tables, views, etc. in the db. I only did this to experiment.<o:p></o:p></li></ol></div><div><p class=xmsonormal><span style='color:black'> </span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>My typical restore command looks like this:<br>pg_restore --verbose --format=custom --dbname=my_db /tmp/my_db_schema_only.backup </span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>(plus some options to capture the output) </span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'> </span><o:p></o:p></p></div><div><p class=xmsonormal style='margin-bottom:12.0pt'><span style='color:black'>Here's a look at what the command line output looks like when this happens:</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>LOG: server process (PID 52476) was terminated by signal 11: Segmentation fault</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>LOG: terminating any other active server processes</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>LOG: all server processes terminated; reinitializing</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>LOG: database system was interrupted; last known up at 2024-04-23 02:16:49 UTC</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>LOG: database system was not properly shut down; automatic recovery in progress</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>LOG: redo starts at 5/51381960</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>WARNING: could not open directory "base/696372": No such file or directory</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>CONTEXT: WAL redo at 5/51381A48 for Database/DROP: dir 1663/696372</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>WARNING: some useless files may be left behind in old database directory "base/696372"</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>CONTEXT: WAL redo at 5/51381A48 for Database/DROP: dir 1663/696372</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>LOG: invalid record length at 5/52679558: expected at least 24, got 0</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>LOG: redo done at 5/526794E0 system usage: CPU: user: 0.07 s, system: 0.01 s, elapsed: 0.10 s</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>LOG: checkpoint starting: end-of-recovery immediate wait</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>LOG: checkpoint complete: wrote 2699 buffers (16.5%); 0 WAL file(s) added, 1 removed, 0 recycled;</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>B; lsn=5/52679558, redo lsn=5/52679558</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>LOG: database system is ready to accept connections</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'> </span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>In the log file, the section written as the error occurs is something like this...</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'><br>[60419] [6627bcbb.ec03] [2024-04-23 13:50:54.813 UTC] [0]: LOG: statement: GRANT ALL ON TABLE my_schema.my_table TO my_user_name;</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>[60419] [6627bcbb.ec03] [2024-04-23 13:50:54.815 UTC] [0]: LOG: statement: -- Completed on 2024-04-23 13:50:54 UTC</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>[60419] [6627bcbb.ec03] [2024-04-23 13:50:54.815 UTC] [0]: LOG: statement: --</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'> -- PostgreSQL database dump complete</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'> --</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>[59940] [6627b39f.ea24] [2024-04-23 13:50:54.943 UTC] [0]: LOG: server process (PID 60419) was terminated by signal 11: Segmentation fault</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>[59940] [6627b39f.ea24] [2024-04-23 13:50:54.943 UTC] [0]: LOG: terminating any other active server processes</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>[59940] [6627b39f.ea24] [2024-04-23 13:50:54.945 UTC] [0]: LOG: all server processes terminated; reinitializing</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>[60423] [6627bcbf.ec07] [2024-04-23 13:50:55.007 UTC] [0]: LOG: database system was interrupted; last known up at 2024-04-23 13:50:48 UTC</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>[60423] [6627bcbf.ec07] [2024-04-23 13:51:05.511 UTC] [0]: LOG: syncing data directory (fsync), elapsed time: 10.00 s, current path: ./base/897556/1249</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>[60423] [6627bcbf.ec07] [2024-04-23 13:51:12.554 UTC] [0]: LOG: database system was not properly shut down; automatic recovery in progress</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>[60423] [6627bcbf.ec07] [2024-04-23 13:51:12.606 UTC] [0]: LOG: redo starts at E/3A8785A8</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>[60423] [6627bcbf.ec07] [2024-04-23 13:51:12.607 UTC] [0]: WARNING: could not open directory "base/562219": No such file or directory</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>[60423] [6627bcbf.ec07] [2024-04-23 13:51:12.607 UTC] [0]: CONTEXT: WAL redo at E/3A878690 for Database/DROP: dir 1663/562219</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>[60423] [6627bcbf.ec07] [2024-04-23 13:51:12.607 UTC] [0]: WARNING: some useless files may be left behind in old database directory "base/562219"</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>[60423] [6627bcbf.ec07] [2024-04-23 13:51:12.607 UTC] [0]: CONTEXT: WAL redo at E/3A878690 for Database/DROP: dir 1663/562219</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>[60423] [6627bcbf.ec07] [2024-04-23 13:51:12.704 UTC] [0]: LOG: invalid record length at E/3BACDAF8: expected at least 24, got 0</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>[60423] [6627bcbf.ec07] [2024-04-23 13:51:12.704 UTC] [0]: LOG: redo done at E/3BACDA80 system usage: CPU: user: 0.07 s, system: 0.01 s, elapsed: 0.09 s</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>[60424] [6627bcbf.ec08] [2024-04-23 13:51:12.804 UTC] [0]: LOG: checkpoint starting: end-of-recovery immediate wait</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>[60424] [6627bcbf.ec08] [2024-04-23 13:51:13.143 UTC] [0]: LOG: checkpoint complete: wrote 2592 buffers (15.8%); 0 WAL file(s) added, 1 removed, 0 recycled; writ</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>9 s, average=0.001 s; distance=18773 kB, estimate=18773 kB; lsn=E/3BACDAF8, redo lsn=E/3BACDAF8 </span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>[59940] [6627b39f.ea24] [2024-04-23 13:51:13.156 UTC] [0]: LOG: database system is ready to accept connections </span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'> </span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'> </span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>I searched the mail archive and performed some additional web searches based on my observations. Unfortunately, I haven't found a similar-enough incident where I might get suggestions for further troubleshooting. In over 10 years of using PostgreSQL+PostGIS, I've never had to dig this deeply to determine the source of error. I'm looking for advice for further troubleshooting or for shared experiences in similar situations</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'> </span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'>Thank you for your time!</span><o:p></o:p></p></div><div><p class=xmsonormal><span style='color:black'> </span><o:p></o:p></p></div><div id="x_Signature"><p><span style='font-family:"Segoe UI",sans-serif;color:black'>Jeffrey Durrence</span><o:p></o:p></p><p><span style='font-family:"Segoe UI",sans-serif;color:black'>McLean Engineering Company</span><o:p></o:p></p><p><span style='font-family:"Segoe UI",sans-serif;color:black'><a href="http://www.mcleanengineering.com/">www.mcleanengineering.com</a></span><o:p></o:p></p><p><span style='font-family:"Segoe UI",sans-serif;color:black'>Office: 229-985-1148</span><o:p></o:p></p><p><span style='font-family:"Segoe UI",sans-serif;color:black;background:white'>Mobile: 229-798-0480</span><o:p></o:p></p><p> <o:p></o:p></p></div></div></div></div></div></div></body></html>