AnsweredAssumed Answered

PostgreSQL Question

Question asked by marshallrobinson on Jan 23, 2019
Latest reply on Mar 26, 2019 by klee_2

Shot in the dark here. Does anyone know why I would be getting the following postgresql log error? I have an enterprise geodatabase loaded on postgresql on linux and I get this error even when doing a simple editing task for more than ten minutes or so. The feature class I create then get's corrupted and crashes arccatalog.

 

2019-01-23 13:34:02.425 MST [8901] LOG: execute sde_1548275642_3809_161: DECLARE sdecur_3809_161 BINARY CURSOR WITH HOLD FOR select V__68.shape , V__68.objectid from (SELECT /* ArcSDE NORMAL_FILTER */ b.objectid,b.shape FROM ugssde.sde.forfun b WHERE NOT EXISTS (SELECT * FROM ( SELECT SDE_DELETES_ROW_ID,SDE_STATE_ID FROM sde.d68, sde.sde_state_lineages l WHERE SDE_STATE_ID = 0 AND DELETED_AT = l.lineage_id AND l.lineage_name = $1 AND l.lineage_id <= $2 ) d WHERE b.objectid = d.SDE_DELETES_ROW_ID ) UNION ALL SELECT a.objectid,a.shape FROM sde.a68 a INNER JOIN sde.sde_state_lineages l ON a.SDE_STATE_ID = l.lineage_id WHERE NOT EXISTS (SELECT * FROM ( SELECT SDE_DELETES_ROW_ID,SDE_STATE_ID FROM sde.d68, sde.sde_state_lineages l WHERE DELETED_AT = l.lineage_id AND l.lineage_name = $3 AND l.lineage_id <= $4 ) d WHERE (a.objectid = d.SDE_DELETES_ROW_ID) AND (a.SDE_STATE_ID = d.SDE_STATE_ID) ) AND (l.lineage_name = $5 AND l.lineage_id <= $6) ) V__68 where ((V__68.shape && $7) = 't')
2019-01-23 13:34:02.425 MST [8901] DETAIL: parameters: $1 = '230', $2 = '255', $3 = '230', $4 = '255', $5 = '230', $6 = '255', $7 = '380000000500000008001000110F0000200000000000000092AAF9B6A4049DE28EAFB11482CCBF02000082CCBF02C2CCBF020000C2CCBF02'
2019-01-23 13:34:02.432 MST [30562] LOG: server process (PID 8901) was terminated by signal 11: Segmentation fault
2019-01-23 13:34:02.432 MST [30562] DETAIL: Failed process was running: DECLARE sdecur_3809_161 BINARY CURSOR WITH HOLD FOR select V__68.shape , V__68.objectid from (SELECT /* ArcSDE NORMAL_FILTER */ b.objectid,b.shape FROM ugssde.sde.forfun b WHERE NOT EXISTS (SELECT * FROM ( SELECT SDE_DELETES_ROW_ID,SDE_STATE_ID FROM sde.d68, sde.sde_state_lineages l WHERE SDE_STATE_ID = 0 AND DELETED_AT = l.lineage_id AND l.lineage_name = $1 AND l.lineage_id <= $2 ) d WHERE b.objectid = d.SDE_DELETES_ROW_ID ) UNION ALL SELECT a.objectid,a.shape FROM sde.a68 a INNER JOIN sde.sde_state_lineages l ON a.SDE_STATE_ID = l.lineage_id WHERE NOT EXISTS (SELECT * FROM ( SELECT SDE_DELETES_ROW_ID,SDE_STATE_ID FROM sde.d68, sde.sde_state_lineages l WHERE DELETED_AT = l.lineage_id AND l.lineage_name = $3 AND l.lineage_id <= $4 ) d WHERE (a.objectid = d.SDE_DELETES_ROW_ID) AND (a.SDE_STATE_ID = d.SDE_STATE_ID) ) AND (l.lineage_name = $5 AND l.lineage_id <= $6) ) V__68 where ((V__68.shape && $7) = 't')
2019-01-23 13:34:02.432 MST [30562] LOG: terminating any other active server processes
2019-01-23 13:34:02.433 MST [792] WARNING: terminating connection because of crash of another server process
2019-01-23 13:34:02.433 MST [792] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2019-01-23 13:34:02.433 MST [792] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2019-01-23 13:34:02.433 MST [22353] WARNING: terminating connection because of crash of another server process
2019-01-23 13:34:02.433 MST [22353] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2019-01-23 13:34:02.433 MST [22353] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2019-01-23 13:34:02.434 MST [790] WARNING: terminating connection because of crash of another server process
2019-01-23 13:34:02.434 MST [790] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2019-01-23 13:34:02.434 MST [790] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2019-01-23 13:34:02.442 MST [30562] LOG: all server processes terminated; reinitializing
2019-01-23 13:34:02.457 MST [12107] LOG: database system was interrupted; last known up at 2019-01-23 13:32:21 MST
2019-01-23 13:34:02.495 MST [12107] LOG: database system was not properly shut down; automatic recovery in progress
2019-01-23 13:34:02.496 MST [12107] LOG: redo starts at 0/BD9C2368
2019-01-23 13:34:02.497 MST [12107] LOG: invalid record length at 0/BD9E0E78: wanted 24, got 0
2019-01-23 13:34:02.497 MST [12107] LOG: redo done at 0/BD9E0D50
2019-01-23 13:34:02.497 MST [12107] LOG: last completed transaction was at log time 2019-01-23 13:33:51.462835-07
2019-01-23 13:34:02.508 MST [30562] LOG: database system is ready to accept connections

Outcomes