[
http://opencast.jira.com/browse/MH-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28975#comment-28975
]
Greg Logan commented on MH-8462:
--------------------------------
>From the docs at http://www.postgresql.org/docs/8.3/static/sql-vacuum.html
"We recommend that active production databases be vacuumed frequently (at least
nightly), in order to remove dead rows. After adding or deleting a large number
of rows, it might be a good idea to issue a VACUUM ANALYZE command for the
affected table. This will update the system catalogs with the results of all
recent changes, and allow the PostgreSQL query planner to make better choices
in planning queries."
Sounds like it needs to be run manually, lame. This isn't a bug with our
stuff, this is a (huge) failure within Postgres.
> capture_agent_state table gets extremly big in postgresql
> ---------------------------------------------------------
>
> Key: MH-8462
> URL: http://opencast.jira.com/browse/MH-8462
> Project: Matterhorn Project
> Issue Type: Bug
> Components: Architecture & Services
> Affects Versions: 1.3
> Reporter: Ruediger Rolf
> Assignee: Denis Meyer
> Priority: Release Blocker
> Fix For: 1.3
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://opencast.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
