Re: PANIC: could not write to log file

From: "Cyril VELTER" <cyril(dot)velter(at)metadys(dot)com>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PANIC: could not write to log file
Date: 2012-11-26 10:26:24
Message-ID: 2674.3532669@A0B26CC9.AE6B.4C00.9DB4.128BBA13E61B
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 23/11/12 17:24:48 mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us wrote :
> "Cyril VELTER" <cyril(dot)velter(at)metadys(dot)com> writes:
> > I follow up on my previous message. Just got two more crash today very similar to the first ones :
>
> > PANIC: could not write to log file 118, segment 237 at offset 2686976, length 5578752: Invalid argument
> > STATEMENT: COMMIT
> > PANIC: could not write to log file 118, segment 227 at offset 9764864, length 57344: Invalid argument
> > STATEMENT: COMMIT
>
> Hm, those write lengths seem rather large. What have you got
> wal_buffers set to? Does it help if you back it off to whatever you
> were using in the 8.2 installation? (The default back in 8.2 days
> seems to have been 64kB, if that helps.)

I changed wal_buffer to 64kb friday evening. It worked flawlessly this week end (but with very litlle load). I got another PANIC this morning with the same kind of message, but just before there is a FATAL :

FATAL: could not create signal handler thread
PANIC: could not write to log file 121, segment 168 at offset 9592832, length 8192: Invalid argument

Unfortunatly there is no error code in the FATAL message.

Best regards,

cyril

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2012-11-26 12:43:36 Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY
Previous Message Chen Huajun 2012-11-26 06:04:05 Re: fix ecpg core dump when there's a very long struct variable name in .pgc file