IDP V3: LockTimeoutException with remote PG DB

[Daniel Fisher]

On Tue, Oct 13, 2015 at 8:53 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 10/13/15, 8:47 AM, "users on behalf of Cantor, Scott" <
> users-bounces at shibboleth.net on behalf of cantor.2 at osu.edu> wrote:
>
>
>
> >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:
> >
> >>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
>
> Actually it's worse, it's loading every record and then doing a check on
> the expiration, so it's doing a ton of selects, yes. That's definitely
> something we need to fix.
>
> I assume/hope we can bypass the JPA abstraction and just issue a single
> delete. That's all it should need to do to clean up the table.


Marvin mentioned to me that the delete appeared inefficient when he ran his
test. Filed this issue for 3.2:
https://issues.shibboleth.net/jira/browse/OSJ-133

--Daniel Fisher
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20151013/340bb218/attachment-0001.html>