<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Automatically removing dead processes from AWS Aurora PostreSQL Geodatabase in Geodatabase Questions</title>
    <link>https://community.esri.com/t5/geodatabase-questions/automatically-removing-dead-processes-from-aws/m-p/1555508#M9386</link>
    <description>&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;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 ?&lt;/P&gt;</description>
    <pubDate>Tue, 05 Nov 2024 17:32:38 GMT</pubDate>
    <dc:creator>ChrisUnderwood</dc:creator>
    <dc:date>2024-11-05T17:32:38Z</dc:date>
    <item>
      <title>Automatically removing dead processes from AWS Aurora PostreSQL Geodatabase</title>
      <link>https://community.esri.com/t5/geodatabase-questions/automatically-removing-dead-processes-from-aws/m-p/1555508#M9386</link>
      <description>&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;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 ?&lt;/P&gt;</description>
      <pubDate>Tue, 05 Nov 2024 17:32:38 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/automatically-removing-dead-processes-from-aws/m-p/1555508#M9386</guid>
      <dc:creator>ChrisUnderwood</dc:creator>
      <dc:date>2024-11-05T17:32:38Z</dc:date>
    </item>
    <item>
      <title>Re: Automatically removing dead processes from AWS Aurora PostreSQL Geodatabase</title>
      <link>https://community.esri.com/t5/geodatabase-questions/automatically-removing-dead-processes-from-aws/m-p/1606541#M9567</link>
      <description>&lt;P&gt;For ref, this was logged as&amp;nbsp;BUG-000172096, "&lt;EM&gt;Connections and locks from referenced services are never removed from Amazon Web Services (AWS) Aurora PostgreSQL geodatabase&lt;/EM&gt;." and is Fixed in "&lt;EM&gt;3.5, 11.5, 3.1.8, 3.4.3&lt;/EM&gt;"&lt;/P&gt;</description>
      <pubDate>Wed, 16 Apr 2025 16:20:39 GMT</pubDate>
      <guid>https://community.esri.com/t5/geodatabase-questions/automatically-removing-dead-processes-from-aws/m-p/1606541#M9567</guid>
      <dc:creator>ChrisUnderwood</dc:creator>
      <dc:date>2025-04-16T16:20:39Z</dc:date>
    </item>
  </channel>
</rss>

