From: | "E(dot) Lefty Kreouzis" <lefty(at)internet(dot)gr> |
---|---|
To: | Florian Weimer <fw(at)deneb(dot)enyo(dot)de> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Growing pg_xlog |
Date: | 2003-07-15 07:41:48 |
Message-ID: | 3F13B03C.6020207@internet.gr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Florian Weimer wrote:
>On Mon, Jul 14, 2003 at 12:55:19PM -0400, Tom Lane wrote:
>
>
>
>>Florian Weimer <fw(at)deneb(dot)enyo(dot)de> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Nigel Bishop | 2003-07-15 14:21:04 | Installing plpgsql gives error |
Previous Message | Zeno R.R. Davatz | 2003-07-15 05:23:01 | Re: corrupt data - caused by lm-sensors? |