Grouper Users - Open Discussion List

["Hyzer, Chris" <>]

Weve switched the grouper built in daemon queries to select all the data that 
needs updating, then do the updates for ~200 rows at a time (since 200 is max 
bind var limit in some DBs).  We haven't done this for the DDL upgrades but 
maybe we should discuss it.  So you could use a procedural block to do this, 
do you need our help to code this?

Thanks
Chris

-----Original Message-----
From: 

 
[mailto:]
 On Behalf Of Jim Fox
Sent: Monday, July 16, 2018 12:44 PM
To: Redman, Chad 
<>
Cc: 

Subject: RE: [grouper-users] upgrade db from 28 to 29 seems to hang


There are about 40M audit records.  Any idea the best way to do the update 
in pieces?  I think postgres update does not support a 'limit' parameter.

Jim

On Mon, 16 Jul 2018, Redman, Chad wrote:

> Date: Mon, 16 Jul 2018 09:37:56
> From: "Redman, Chad" 
> <>
> To: Jim Fox 
> <>,
>     
> ""
>  
> <>
> Subject: RE: [grouper-users] upgrade db from 28 to 29 seems to hang
> 
> Sounds like a query plan gone wrong. Are the statistics relatively recent?
>
> If there is a large number of rows in the table, the row updates may need 
> to be done in small batches. Depending on the database, large scale updates 
> sometimes take long because it needs to archive the pre-changed data for a 
> potential rollback.
>
> -Chad
>
>
> -----Original Message-----
> From: 
> 
>  
> [mailto:]
>  On Behalf Of Jim Fox
> Sent: Thursday, July 05, 2018 12:01 PM
> To: 
> 
> Subject: [grouper-users] upgrade db from 28 to 29 seems to hang
>
>
> I'm doing a database upgrade and at the end of the 28->29 step it runs the
> command
>
>> update grouper_audit_entry set act_as_member_id=logged_in_member_id where 
>> act_as_member_id is null and logged_in_member_id is not null;
>
>
> which seems to just sit forever.  ( as in more than a day )
>
> Could I skip this step for now and finish to conversion to version 30?  I 
> could complete the update of the audit entries later.
>
> Would that work?
>
> Thanks,
>
> Jim
>
>