From: | Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> |
---|---|
To: | mzhang(at)ilww(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: org.postgresql.util.PSQLException: PANIC: could not write to log file 6 |
Date: | 2009-07-30 11:43:51 |
Message-ID: | C7097320-CEC3-404C-994A-A063FFFC887D@solfertje.student.utwente.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 29 Jul 2009, at 14:43, mzhang(at)ilww(dot)com wrote:
> Hello,
>
> In our customer site, the following error occurred. I tried to find
> some
> indication what this means. Is this log file used for the roll back
> purpose? In what scenario that one gets such fatal error?
It's likely part of the WAL, in which case there would be data loss if
it can't write there.
> Caused by: org.postgresql.util.PSQLException: PANIC: could not write
> to
> log file 6, segment 176 at offset 14991360, length 8192: Read-only
> file
> system
You missed the interesting part: "Read-only file system".
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4a71877c10135591761324!
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2009-07-30 11:44:13 | Re: Clients disconnect but query still runs |
Previous Message | Craig Ringer | 2009-07-30 11:40:03 | Re: Clients disconnect but query still runs |