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 On Thu, Apr 8, 2010 at 4:06 PM, Alvaro Herrera <alvhe...@commandprompt.com> wrote: > Steven Harms escribió: >> I ran into a script today that was removing files under >> /var/lib/pgsql/data/pg_clog today because they were too large >> (Postgresql 7.4). My initial thought was this could cause data loss >> or corruption, can someone provide insight as to if that is correct? > > Yeah. How large? > > -- > Alvaro Herrera http://www.CommandPrompt.com/ > The PostgreSQL Company - Command Prompt, Inc. > -- GPG Key ID: C92EF367 / 1428 FE8E 1E07 DDA8 EFD7 195F DCCD F5B3 C92E F367 WWW: http://www.sharms.org/blog -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
