Recently we had a citation where our postgres db was consuming our space allocation of 30 GB. This did not seem right, and we realized that we had never run "vacuum --full". When this was run, tons of memory was freed-up. Today, I'm running index-all, and the portion that "Indexes all items in Dspace..." has been running now for close to 4 hours. Last week when I ran index-all, this portion of the script took about 1 hour to run. I'm getting a bit concerned. Does this make sense to any one? Unfortunately, when this portion of index-all runs there are no writes to log the file ( I have INFO set, not DEBUG ), so I have no idea if things are progressing smoothly or not.
Thanks for any thoughts on this. Jose ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
