On 13-05-2016 19:04, Alvaro Herrera wrote:
I happened to notice this report from 15 months ago, which didn't get
any response. Did you find a solution to this problem? I would first
blame btrfs, mostly because I've never heard of anyone with this problem
on more mainstream filesystems. As I r
Alvaro Herrera writes:
> Gustavo Lopes wrote:
>> ... Why wouldn't postgres retry on EINTR or even
>> allow return values of write() lower than nbytes (and then continue in a
>> loop).
> I happened to notice this report from 15 months ago, which didn't get
> any response. Did you find a solution
Gustavo Lopes wrote:
> Every few weeks, I'm getting a error like this:
>
> > 2015-02-11 15:31:00 CET PANIC: could not write to log file
> > 00010007007D at offset 1335296, length 8192: Interrupted system
> > call
> > 2015-02-11 15:31:00 CET STATEMENT: COMMIT
> > 2015-02-11 15:31:17 C
Every few weeks, I'm getting a error like this:
> 2015-02-11 15:31:00 CET PANIC: could not write to log file
> 00010007007D at offset 1335296, length 8192: Interrupted system
> call
> 2015-02-11 15:31:00 CET STATEMENT: COMMIT
> 2015-02-11 15:31:17 CET LOG: server process (PID 8390) w
Every few weeks, I'm getting a error like this:
> 2015-02-11 15:31:00 CET PANIC: could not write to log file
> 00010007007D at offset 1335296, length 8192: Interrupted system
> call
> 2015-02-11 15:31:00 CET STATEMENT: COMMIT
> 2015-02-11 15:31:17 CET LOG: server process (PID 8390) w
