View Issue Details

IDProjectCategoryView StatusLast Update
0013726Tine 2.0Tinebasepublic2018-03-08 16:13
Reporternbe-renzel-netAssigned Topschuele 
PrioritynormalSeveritytweakReproducibilityalways
Status feedbackResolutionopen 
Product Version 
Target VersionFixed in Version 
Summary0013726: table "container_content": over 13041450 rows - in words: thirteen million rows - how to cleanup?
DescriptionWe're syncing our Tine20 installation with our Active Directory every hour using a cron job. Tine20 has been running for about 10 months now.

The PostgreSQL dumps are growing and growing - about 6 MB larger every day (gzip'ed compressed dumps). And I wondered why.

Looking at the database directly, I see that the table "tine20_container_content" now contains about 13 million rows. Most rows are for "container_id=1" which equals to our "Internal Contacts" that are updated with every Active Directory sync.

Is that really neccessary that this table grows so large? Are there any caveats if I delete all entries "WHERE container_id=1 AND action='update'"? I see that this table is used within the "syncotron" library so I better ask here before I delete the - in my eyes - unneccessary entries.

TIA and regards,
Nils
TagsNo tags attached.
mwticket

Activities

pschuele

pschuele

2018-03-08 16:13

administrator   ~0021490

if you don't use activesync or carddav, it should be no problem to remove the records with container_id = 1 from there.

we'll talk about this and maybe will provide a cleanup script that removes the obsolete records from the table.

but the ad sync should not update the records in each sync process. maybe there is something wrong there, too? perhaps you could check the logs of the user sync (and/or the contact history) and check the fields that are updated in each sync.

Issue History

Date Modified Username Field Change
2018-01-23 14:58 nbe-renzel-net New Issue
2018-03-08 16:13 pschuele Note Added: 0021490
2018-03-08 16:13 pschuele Assigned To => pschuele
2018-03-08 16:13 pschuele Status new => feedback