Alvaro Herrera wrote: > Steven Harms escribi?: > > I don't have stats on how big they were getting, but they are running > > this every night, which I suspect causes issues (and I suspect the > > reason their logs were getting big is because they programmed a bunch > > of locked transactions): > > > > find /pgsql/data/pg_xlog -type f -mtime +1 | xargs rm -f > > find /pgsql/data/pg_clog -type f -mtime +1 | xargs rm -f > > Oh, the *directories* were getting big, not the files? (Normally > pg_clog files do not grow beyond a certain, rather small size, which is > why I was asking) Yeah, they are bound to lose or corrupt data sooner > rather than later. If they ever see their system crash, it won't be > able to recover due to pg_xlog deletion. (Note that pg_xlog is quite > different from pg_clog). pg_clog deletion guarantees that they will > have problem vacuuming or something.
My guess is that they are not vacuuming all databases so old clog files cannot be removed. That, combined with the fact they are runing 7.4 would incline me to get as far away from that system as possible so as not be blamed for the predictable problems. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
