Automating removal of orphaned stored procedure calls - Mailing list pgsql-admin

From John Scalia
Subject Automating removal of orphaned stored procedure calls
Date
Msg-id 60D4E7CB-BA42-4203-A5EF-9E5FA4D7CAE3@gmail.com
Whole thread Raw
Responses Re: Automating removal of orphaned stored procedure calls
List pgsql-admin
One of our newer applications is regularly leaving some stored procedures in a partially completed state. It’s not one
ofmy applications, and the DBA responsible for it hasn’t said why this happens, but he is trying to automate removing
these.Currently, it’s a manual process where they log into the db as the application owner which owns these and remove
themmanually. For whatever reason he can’t use the application owner’s I’d to run this process. I suggested adding the
applicationowner as a group for the actual user he is going to use, and once that happened, using a SET ROLE to become
thatuser, but it did not apparently work. Anybody have any good ideas here to make this work? 

Sent from my iPad


pgsql-admin by date:

Previous
From: Mladen Gogala
Date:
Subject: Re: Improve "select count(*)" query - takes more than 30 mins for some large tables
Next
From: Holger Jakobs
Date:
Subject: Re: Automating removal of orphaned stored procedure calls