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):
> >
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
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 /pgs
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
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?
Thanks,
Steve
--
GPG Key ID: C92EF367 /
