IDP V3: LockTimeoutException with remote PG DB
Cantor, Scott
cantor.2 at osu.edu
Tue Oct 13 08:47:49 EDT 2015
On 10/13/15, 5:29 AM, "users on behalf of TISSOT Jacques" <users-bounces at shibboleth.net on behalf of jacques.tissot at unifr.ch> wrote:
>I could schedule this to 1 day, so that it occurs during the night, huh?
I suppose, but there's something seriously wrong if that's necessary.
>What is running behind this storage.cleanup, making a lot of "SELECT waiting"?
It should be a single delete statement, but it looks like it's doing this and then a delete per result record:
SELECT distinct r.context FROM JPAStorageRecord r
That should still be quite fast but I would suggest Daniel consider just doing a straight delete against the whole table for expired records rather than looking at each context individually.
I would have to assume you're missing an index if that's really causing problems, or we have a connection holding open a transaction/lock.
-- Scott
More information about the users
mailing list