Hello Geodatabase, when using an AWS Aurora PostgreSQL Geodatabase I am seeing dead processes permanently left in the sde_process_information table, and their associated locks in the sde_table_locks table.
While a dead process can sometimes occur, on a non-AWS Geodatabase this is removed after a while, but on an AWS Aurora PostgreSQL Geodatabase Geodatabase it remains permanently.
I believe the Geodatabase function SDE_PURGE_PROCESSES should be tidying these up, but on AWS Aurora PostreSQL this seems to be failing. Does anyone have any suggestions or recommendations around this ?
