From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Steven Harms <thisdyingdream(at)gmail(dot)com> |
Cc: | Pg General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Removing files under pg_clog |
Date: | 2010-04-08 20:35:37 |
Message-ID: | 20100408203537.GC4127@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
--
Alvaro Herrera http://www.advogato.org/person/alvherre
"And as an added bonus, now my computer goes to the toilet for me, leaving me
free to spend time on more useful activities! yay slug codefests!" (C. Parker)
From | Date | Subject | |
---|---|---|---|
Next Message | Corin | 2010-04-08 20:54:38 | Re: fulltext search stemming/ spelling problems |
Previous Message | Steven Harms | 2010-04-08 20:15:18 | Re: Removing files under pg_clog |