Re: Old pg_xlog files
| От | Tass Chapman |
|---|---|
| Тема | Re: Old pg_xlog files |
| Дата | |
| Msg-id | ec9575e80603230510k2b36080fi4e10b9dbddbcdbe2@mail.gmail.com обсуждение |
| Ответ на | Re: Old pg_xlog files (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-general |
Thanks.
I'll see if I can get a scheduled maintenance check on this.
The disks seem to be good as they are a 0+1 RAID and all internal tests show them to be in good health along with the controller. Would memory be a good suspect?
I'll see if I can get a scheduled maintenance check on this.
The disks seem to be good as they are a 0+1 RAID and all internal tests show them to be in good health along with the controller. Would memory be a good suspect?
On 3/22/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"Tass Chapman" <tasseh.postgres@gmail.com> writes:
> Any suggestions on what I can look at to see why the checkpoint was so far
> outstanding and why it hung on in a Zombie state when we tried a soft boot?
If it was in a funny process state, I'd guess that there was some
hardware problem that caused a disk write request to hang up. You
can get stuck in uninterruptible disk wait for quite a long time if
the disk doesn't respond.
regards, tom lane
В списке pgsql-general по дате отправления: