Re: Hard limit on WAL space used (because PANIC sucks) - Mailing list pgsql-hackers

From MauMau
Subject Re: Hard limit on WAL space used (because PANIC sucks)
Date
Msg-id 4B4E81C123184410B92AA8E8EBA73C7A@maumau
Whole thread Raw
In response to Re: Hard limit on WAL space used (because PANIC sucks)  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
From: "Joshua D. Drake" <jd@commandprompt.com>
> On 06/08/2013 11:27 AM, Andres Freund wrote:
>> You know, the PANIC isn't there just because we like to piss of
>> users. There's actual technical reasons that don't just go away by
>> judging the PANIC as stupid.
>
> Yes I know we aren't trying to piss off users. What I am saying is that it 
> is stupid to the user that it PANICS. I apologize if that came out wrong.

I've experienced PANIC shutdown several times due to WAL full during 
development.  As a user, one problem with PANIC is that it dumps core.  I 
think core files should be dumped only when "can't happen" events has 
occurred like PostgreSQL's bug.  I didn't expect postgres dumps core simply 
because disk is full.   I want postgres to shutdown with FATAL message in 
that exact case.

Regards
MauMau




pgsql-hackers by date:

Previous
From: "MauMau"
Date:
Subject: Re: Hard limit on WAL space used (because PANIC sucks)
Next
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Don't downcase non-ascii identifier chars in multi-byte encoding