From: Holger Jakobs <holger@jakobs.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Automating removal of orphaned stored procedure calls
Date: Tue, 12 Jul 2022 19:10:10 +0200
Message-ID: <17ace17d-eff0-f198-7bbc-74c87957a8ae@jakobs.com> (raw)
In-Reply-To: <60D4E7CB-BA42-4203-A5EF-9E5FA4D7CAE3@gmail.com>
References: <60D4E7CB-BA42-4203-A5EF-9E5FA4D7CAE3@gmail.com>
Am 12.07.22 um 18:58 schrieb John Scalia:
> One of our newer applications is regularly leaving some stored procedures in a partially completed state. It’s not one of my 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 them manually. For whatever reason he can’t use the application owner’s I’d to run this process. I suggested adding the application owner as a group for the actual user he is going to use, and once that happened, using a SET ROLE to become that user, but it did not apparently work. Anybody have any good ideas here to make this work?
> Sent from my iPad (How nice you are advertising the device you are using. Is this relevant to your question?)
I cannot see any connection between a transaction "hanging" and the
usage of stored procedures. Of course it can happen anywhere, if a
transaction is trying to update rows another transaction has updated
without having completed.
Try to find out by looking into pg_locks what is happening.
--
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
Attachments:
OpenPGP_signature (application/pgp-signature, 202B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: holger@jakobs.com, pgsql-admin@lists.postgresql.org
Subject: Re: Automating removal of orphaned stored procedure calls
In-Reply-To: <17ace17d-eff0-f198-7bbc-74c87957a8ae@jakobs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox