Florian Weimer wrote:

On Mon, Jul 14, 2003 at 12:55:19PM -0400, Tom Lane wrote:



Florian Weimer <[EMAIL PROTECTED]> writes:


I seem to have some obscure problem with the WAL logs (AFAIK that's what
is stored in the pg_xlog directory):


63G /var/lib/postgres/data/pg_xlog


This is a bit too much wasted space for my taste. 8-/


The only theory that comes to mind is that the automatically issued
checkpoint operations are failing before they get to the stage of
truncating the WAL. Is there anything suspicious looking in the
postmaster log?



No, I'm afraid. However, the checkpoint subprocess was stuck in the "T" state (meaning that it had received SIGSTOP). 8-/




Ah, running on linux 2.4 I suppose. There is a known bug if someone 'strace's a process and the kills the strace process the traced process is stuck in the T state and needs kill -SIGCONT to continue


Lefty


---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend

Reply via email to