这是我有的:
> ps -ef | grep -i vacuum
没有显示自动真空过程.
>使用psql控制台,显示autovacuum,表示其值为ON
>从FROM pg_stat_user_tables使用psql控制台,SELECT schemaname,relname,last_vacuum,last_autovacuum;在last_vacuum和last_autovacuum列中没有给出任何值,即使我使用pgadmin3进行了手动真空维护功能.
> pgadminIII中db的属性选项卡表示’未运行’的autoVACUUM值
我错过了什么?
编辑
当我试图在服务器上找到文件时,我也无法访问Openshift Online上的postgresql.conf – 希望手动编辑文件而不是使用pgadminIII.
– 发现这个https://www.openshift.com/forums/openshift/how-do-i-set-maxpreparedtransactions-on-my-postgresql-cartrIDge我现在能够查看/编辑我的postgresql.conf.显然autovacuum已经打开,因此conf具有正确的设置.
当问题pg_ctl重启-m fast我得到了
LOG: Could not bind socket for statistics collector: Permission denIEd LOG: trying another address for the statistics collector LOG: Could not bind socket for statistics collector: Permission denIEd LOG: trying another address for the statistics collector LOG: Could not bind socket for statistics collector: Cannot assign requested address LOG: trying another address for the statistics collector LOG: Could not bind socket for statistics collector: Cannot assign requested address LOG: disabling statistics collector for lack of working socket WARNING: autovacuum not started because of misconfiguration HINT: Enable the "track_counts" option. LOG: database system was shut down at 2014-04-22 09:58:19 GMT LOG: database system is ready to accept connections
虽然在postgresql.conf中已将track_counts设置为on
很抱歉这么愚蠢,但任何帮助或指示非常感谢.
先感谢您.
… for some insane reason,openshit Disabled localhost,and autovacuum only connects to localhost,I suppose it makes sense that they wouldn’t want to be trying to vacuum a remote db… but openshit breaks autovacuum.
我找到的一个解决方案(我可能会使用)是手动添加一个强制真空的cronjob. here是一个看起来很有前途的批处理脚本,但要注意强制真空可能涉及的副作用(当然取决于你的app).
总结以上是内存溢出为你收集整理的postgresql – Autovacuum未在Openshift Online Postgres盒式磁带上运行全部内容,希望文章能够帮你解决postgresql – Autovacuum未在Openshift Online Postgres盒式磁带上运行所遇到的程序开发问题。
如果觉得内存溢出网站内容还不错,欢迎将内存溢出网站推荐给程序员好友。
欢迎分享,转载请注明来源:内存溢出
评论列表(0条)